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

Annotations already indicate readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral context: that results are 'ready to call directly, no second schema lookup needed,' and that it provides an option set rather than a single answer, complementing annotations without 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 a single block of four sentences that front-loads purpose and usage. It includes necessary details (domain examples, return format) with no redundancy or fluff, achieving high efficiency.

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 tool's discovery role, the description fully covers what it does, when to use it, what it returns (schemas, examples), and its behavior (no second lookup). Without an output schema, the description adequately explains return value.

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?

Although schema coverage is 100% with descriptions for all 6 parameters, the description does not significantly expand on their meaning beyond the schema. It notes aliases (task, q, description, search) which are already documented. Score reflects adequate but not extra value.

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's purpose as 'Find tools by describing the data or task.' It indicates discovery, browsing, and searching for tools across specified domains, and highlights that it returns 'top-N most relevant tools with names, descriptions, and full input schemas,' distinguishing it from sibling tools.

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 tells when to use the tool: 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' It also lists specific use cases (SEC filings, financials, etc.), providing clear guidance on context.

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