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

Though annotations are absent, description discloses that output is a result list to be passed to a fetch tool, implying read-only behavior. No side effects or destructive actions hinted. Could be more explicit about non-destructiveness but sufficient for a search tool.

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?

Three sentences, front-loaded with verb and scope, then output usage, then alternative guidance. No filler, each sentence serves a distinct purpose.

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 single parameter with full schema coverage and existence of output schema, description covers search scope, output usage, and sibling differentiation comprehensively. No gaps identified.

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?

Parameter 'query' is fully described in schema with examples. Description reinforces by listing types but adds no new semantic details beyond schema. Baseline score for 100% schema coverage.

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?

Description clearly states verb 'search' and specifies resources (tokens, programs, pools) across multiple chains. Explicitly distinguishes from sibling tools by directing to specialist tools when entity type 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?

Provides explicit guidance: use this tool for broad keyword search, and use specialist tools (search_tokens, discover_programs, aex402_listPools) when entity type is known, fulfilling when-to-use and when-not-to.

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