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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, so the bar is low, and the description still adds meaningful behavior: the catalog is bounded to 13 items, the return is matching form summaries plus verified PDF links, and it explicitly does not touch the web. The main omission is pagination/ordering behavior of the result set.

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 dense sentences, front-loaded with what is searched and how, followed by output shape and explicit boundaries. No filler or restatement of the tool name.

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 an output schema present, the description need not explain return values — yet it still summarizes them, and annotations carry the safety profile. Scope, boundaries, and query semantics are all covered; the only real gap is the undocumented vehicle_type filter, which matters for a multi-vehicle-type catalog.

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 0% across 3 parameters, so the description must carry the load. It adds useful meaning for 'query' ('short topic', topic words not personal details), but says nothing about 'vehicle_type' (an enum filter with a default of 'rv') and only glancingly implies 'limit' via 'catalog of 13'. One of three parameters is effectively undocumented.

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?

Clear verb + resource with hard scope: 'Search a bounded catalog of 13 free blank U.S. campervan/RV worksheets by a short topic.' That is far more specific than a generic search tool, and it rules out web search and advice. However, no sibling (e.g., get_rv_worksheet for a single form, get_rv_library_info for catalog facts) is named, so the search-vs-fetch distinction is left to inference.

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?

It gives one real usage instruction ('Use topic words, not personal details') and negative scope ('does not search the web or provide general RV advice'), which implicitly steers agents away from advice/planning siblings. But it never states when to choose this over get_rv_worksheet or get_rv_library_info, so the routing guidance is only implied.

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