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

Annotations already declare readOnlyHint, idempotentHint and non-destructive/openWorld behavior, lowering the bar. The description adds real value beyond that: it discloses the return format (contextual content with titles and direct links) and the concrete chaining pattern (append .mdx, read with head -200). It stops short of mentioning result limits or pagination, keeping it out of the top band.

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 with the purpose and routing guidance before the detailed .mdx chaining tip, and every sentence serves a distinct function. The final sentence is long and example-heavy, but the specificity is genuinely useful rather than filler.

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?

With no output schema, the description compensates by describing what search returns (titles and direct links) and how to escalate to full content via the sibling tool. For a one-parameter read tool with full annotation coverage, an agent has everything needed to call it and follow up correctly.

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% for the single `query` parameter, so the schema already carries the semantics. The description hints at query intent through the use-case examples but adds no syntax, format, or matching-behavior detail beyond the schema. 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?

States a specific verb (search) and resource (Metabind knowledge base), enumerating the content types it covers (code examples, API references, guides). It distinguishes itself from query_docs_filesystem by naming what that sibling is for, so an agent can tell them apart without opening either schema.

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 says when to use it (answer questions about Metabind, find docs, understand features, locate implementation details) and names the alternative with its triggering condition (need full page content → query_docs_filesystem with head/cat). Nothing is left to inference.

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