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

Annotations already mark it read-only and idempotent; the description adds that results are 'ready to call directly, no second schema lookup needed,' which is useful behavioral context beyond safety hints. No contradictions with the annotations.

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 concise sentences cover purpose, usage context, and return value. The description is front-loaded with the core action ('Find tools'), and every sentence adds substantive information without redundancy.

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 covers what it does, when to use it, what it returns, and the scope of domains. With no output schema, it still explains the return structure (top-N tools with names, descriptions, and full input schemas) sufficiently for an agent to invoke and use results.

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 descriptions for query, limit, and multiple aliases. The description reinforces the natural-language query behavior and lists example queries, but adds no parameter-specific details beyond the schema, so baseline 3 is appropriate.

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 opens with 'Find tools by describing the data or task,' clearly identifying the verb (find) and resource (tools). It distinguishes itself from sibling tools by being the only tool-discovery meta-tool, and the listed domains (SEC filings, FDA drugs, etc.) further scope its purpose.

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?

Explicitly states '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.' This gives clear when-to-use guidance without needing to infer context.

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