search

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds behavioral details: 'Read-only and keyless', and explains that no matches return empty arrays not errors. It also clarifies limit is applied client-side.

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 well-organized paragraph that front-loads the main purpose, then covers return, usage context, behavior, and parameter details. No wasted words.

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?

The description fails to mention the required 'rationale' parameter, which is present in the schema. This is a significant omission for a parameter that must be supplied. Otherwise, the description covers most other aspects adequately.

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% but the description adds examples for query (e.g., '0x...') and explains limit application. This provides practical guidance beyond the schema.

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 the tool searches across all networks for tokens, pools, and DEXes, returning three arrays. It distinguishes itself by specifying it is the cross-chain entry point when network is unknown, and advises switching to network-scoped tools once a slug is known.

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 explicitly provides when to use (when you do not know the network) and when not (once you have a network slug, use network-scoped tools). It also gives concrete search examples like 'find PEPE' and 'which chain is this token on?'.

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