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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful runtime behavior: results are paragraphs, not whole documents, and all query words must appear. This gives an agent a realistic expectation of the output without an output 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?

Three short sentences, each earning its place: purpose, return shape, and usage guidance. The key constraint (all query words must appear) is stated compactly.

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?

For a simple read-only search tool, the description covers what it does, what it returns, and when to use it. The only minor gap is the unstated meaning of 'limit,' and the absence of an output schema is mitigated by the description's return-value explanation.

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?

The schema describes 'query' and the description reinforces the all-words-must-match semantics, but the 'limit' parameter has no semantic description in either the schema or the description. With only 50% schema description coverage, the description partially compensates but does not fully document the other parameter.

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 a specific verb and resource: 'Full-text search across every classifier.dev document.' It also states the distinctive return shape (paragraphs with document and section), which differentiates it from sibling tools like list_docs and read_doc.

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 last sentence explicitly tells the agent when to choose this tool ('Use it for a specific question') and gives concrete examples, contrasting with 'reading whole documents.' It does not explicitly name sibling tools or state when not to use it, but the usage context is clear.

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