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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds valuable behavior: returns top-N tools with full schemas and curated examples, ready to call directly with no second lookup. No contradiction with annotations; this is meaningful additional context.

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 the core purpose, efficient domain list, and key return-value detail. No fluff; every sentence earns its place.

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?

Despite no output schema, the description specifies exactly what is returned (names, descriptions, schemas, examples) and instructs on when to call it first. Covers return format and usage context sufficiently for a discovery 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% with clear parameter descriptions. The description adds nuance by explaining the query as a natural language description ('describing the data or task'), mentioning the top-N return behavior tied to limit, and providing concrete domain examples that align with query usage.

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 uses a specific verb+resource structure ('Find tools by describing the data or task') and clearly differentiates from siblings by positioning itself as the discovery/meta-tool, with a concrete list of covered domains (SEC filings, FDA drugs, FRED, etc.).

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 when-to-use guidance ('Use when you need to browse, search, look up, or discover what tools exist') and a strong directive to 'Call this FIRST when you have many tools available.' It also implies not for single-answer tasks ('not just one answer'), though it does not name specific alternative tools.

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