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

Annotations declare readOnly, idempotent, and non-destructive, and the description adds concrete behavioral detail: it returns top-N tools with names, descriptions, and full input schemas, 'ready to call directly, no second schema lookup needed.' This exceeds the annotation baseline and clarifies output behavior. No contradiction.

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 front-loaded with the core purpose, then lists relevant domains, return behavior, and usage guidance. The domain list is long but informative for search recall. Each sentence serves a purpose, though it could be slightly tightened without losing value.

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 clearly explains return values ('names, descriptions, and full input schemas') and context ('Call this FIRST when you have many tools available'). For a meta-tool with well-covered annotations, this is complete and sufficient.

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 every parameter has a description, including alias relationships. The description adds no additional parameter semantics beyond what the schema provides, so baseline 3 is appropriate. The mention of 'top-N' aligns with the limit parameter but does not add new detail.

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 a specific verb ('Find') and resource ('tools'), and defines the scope: 'browse, search, look up, or discover what tools exist' for a broad set of data domains. It distinguishes itself from siblings by being a meta-tool for tool discovery, not a task-specific tool.

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 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' This implies when not to use it (when you need a single direct answer) and positions it relative to alternatives.

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