search_docs

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

Describes case-insensitive token scan, ranking by match count, and return of entire cards with specific fields. No contradictions, and covers behavior beyond schema.

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?

Front-loaded purpose, efficient sentences, no fluff. Every sentence adds value: purpose, algorithm, usage guidance.

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 output schema and sibling tools, description is complete: explains return format, ranking, and usage. Lacks pagination info but acceptable for search 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?

With schema coverage at 0%, description compensates by explaining `query` as keyword and `limit` as 'up to limit whole cards,' adding meaning beyond basic schema.

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?

Clearly states verb (search), resource (docs), and outcome (return matching endpoint cards). Distinguishes from siblings like get_endpoint and list_endpoints.

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: 'when you know roughly what you want but not the exact path.' While no direct alternatives are named, sibling tools imply alternatives.

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