Unverified50% confidenceOpinionExact time
When a reasonably capable tool is abandoned, the problem is almost never "not knowing how to use it," but where the tool is placed, how it reports, what it displays and what it is named.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/19/2026
First Seen
Valid until: 1/17/2027
Sources
Related Entities
Related Claims
UnverifiedAs tools multiply, a tool confusion problem arises where tools are not called when they should be and are called when they should not be; the Skill mechanism solves this problem by codifying workflows and significantly improves task completion accuracy.76% similarUnverifiedEven when Skills are not invoked, simply listing them in the available tools list consumes token space in the context window in the form of Tool Definitions.76% similarUnverifiedThe more tools there are and the more similar their descriptions, the overall usability of the entire tool chain may actually be lower than a system with fewer but precisely described tools.75% similarUnverifiedIn Custos, discovering a tool does not equate to authorization to use it; whether a tool is actually available is determined by policy.73% similarUnverifiedWhen mixing inline tools with traditional static tool sets, it is recommended to define clear trigger conditions for each tool change and to write the applicable boundaries of tools clearly in the system message, so as to avoid the model continuing to attempt calls when the old tools are no longer valid.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1065573API
curl https://kongchang.com/api/v1/knowledge/claims/1065573MCP
get_claim(id=1065573)