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

Annotations already declare the tool as safe, idempotent, and non-destructive. The description adds valuable behavioral details: it returns top-N relevant tools with names, descriptions, and full input schemas (with curated examples), ready to call without a second schema lookup.

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 somewhat lengthy but every sentence adds value. It front-loads the primary purpose and provides concrete examples and usage guidance. Minor redundancy in listing domains could be tightened, but overall it's well-structured.

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 the complexity (6 parameters, no output schema, many siblings), the description fully explains what the tool does, when to use it, what it returns (names, descriptions, schemas), and how it integrates into a workflow (call first). No gaps are apparent.

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 description coverage is 100%, so baseline is 3. The description adds context with examples of natural language queries ('analyze housing market trends', 'look up FDA drug approvals') and mentions the limit parameter, providing meaning beyond the schema's terse descriptions.

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 finds tools by describing data/task, lists numerous example domains, and explicitly distinguishes itself from siblings by saying 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).'

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 states when to use (browse, search, look up, discover tools) and provides a clear directive to call this FIRST when many tools exist, implying it should precede other tool calls. It also implies exclusion for getting a single direct answer.

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