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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, and the description adds meaningful non-obvious behavior: alias normalization, the rate-limit cost per search, and the instruction not to fire partial queries. This is exactly the kind of behavioral context annotations cannot convey.

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 front-loaded with the core purpose and then adds return fields, rate-limit guidance, and downstream create_form usage in a logical order. The closing 'Free.' is the only sentence that does little to help an agent invoke the tool correctly, so it falls just short of a perfect conciseness score.

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 one-parameter search tool, the description is complete: it explains what to pass, how the query behaves, what fields are returned, how many rate-limit slots are consumed, and how the result feeds into create_form. The existence of an output schema reduces the need to document return values further, but the description already does so.

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 coverage is 0% and the single required 'query' parameter has no schema description, so the description carries the full burden. It compensates thoroughly by explaining that the query can be a name, number, or alias, and gives concrete examples like 'w9', 'W-9', 'form w 9', and 'taxpayer identification'.

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 uses a specific verb and resource: 'Find a blank government form in the Emboss library by name or number.' It clearly distinguishes this search-and-match behavior from siblings like get_form or list_forms by emphasizing lookup by name/number/alias and returning multiple match summaries.

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 gives clear operational guidance: send the whole query once, do not search as the user types, and be aware each search consumes a rate-limit slot. It also explains how to pass the returned slug to create_form, though it does not explicitly contrast this tool with other lookup siblings such as list_forms or get_form.

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