search_tokens

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears full responsibility. It only mentions search by name/symbol but fails to disclose crucial traits: case sensitivity, partial matching, limit on results, response format, or error behavior. An agent cannot infer what will happen on query.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It is appropriately sized for the tool's simplicity, though it could benefit from additional brief details without sacrificing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema, the description should explain what the tool returns (e.g., list of token objects, matching tokens, or empty array). It does not mention pagination, result limits, or how to interpret results, leaving the agent without sufficient context for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the only parameter 'query' is adequately described as 'Search query (token name or symbol)'. The description confirms this but adds no new meaning beyond the schema, meeting the baseline for adequate parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search for cryptocurrency tokens by name or symbol', specifying a distinct verb and resource. It effectively distinguishes from sibling tools which are all specific getters (e.g., get_token_price, get_btc_balance), making its purpose as a discovery tool unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for finding tokens but does not explicitly state when to use this tool vs alternatives like get_token_price. No context on prerequisites or typical flow (e.g., 'Use this to find token IDs before querying prices') is provided, leaving the agent to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.