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

Discloses that unknown IDs return found:false, which is useful non-obvious behavior not captured by the readOnly/openWorld/destructive annotations. This adds real behavioral context beyond the structured hints.

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?

Two tight sentences: the first delivers the verb, resource, parameter, and example; the second covers the not-found behavior. No filler or repetition.

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 one-parameter lookup tool with an output schema, the description covers the lookup key, example format, and an important edge-case behavior. Nothing essential is missing for correct invocation.

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 input schema only says id is a non-empty string, but the description identifies it as canonical_item_id and gives a realistic example format. This fully compensates for the 0% schema description coverage.

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 the exact operation: 'Lookup one CanonicalSurveyItem by canonical_item_id' and includes a concrete example ID. This clearly distinguishes it from list/search siblings, which work over collections rather than a single keyed lookup.

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 clear context that this tool is for retrieving one item by exact ID. It does not explicitly say 'use search when the ID is unknown,' but the single-ID lookup instruction makes the appropriate use case evident.

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