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

Goes well beyond annotations by disclosing that taxonomy resolution may invoke a paid model under the public spend cap – which actually explains the readOnlyHint=false anomaly on an otherwise read-like tool. It also states explicit non-effects (no submit/contact/reserve/book) and failure semantics ('an unavailable question set is unknown, not permission to invent questions').

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?

Four dense but purposeful sentences, with the core action and the primary input path front-loaded. Every sentence carries distinct information (cost, scope, failure mode), though the phrasing is compressed to the point of feeling slightly terse.

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 needn't document return values, and it instead covers when to call, input selection, cost implications, and non-effects. Only minor gaps remain, such as locale defaulting and what 'public spend cap' means operationally.

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 75%, so the schema does most of the work, but the description adds real meaning: that subcategoryUuid must be a returned value, that requestedService exists only for taxonomy resolution, and that only returned keys/types/options should be used. It does not clarify locale behavior or defaults.

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 and resource ('Read saved canonical questions') scoped to collecting a quote request in Costa Rica. An agent can tell this apart from write-oriented siblings like wellfred_request_quotes, though no sibling is named explicitly to sharpen the contrast.

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?

Gives clear usage timing ('before collecting a quote request') and an input-based branch ('subcategoryUuid, or requestedService for existing taxonomy resolution'). Negative scope ('does not submit, contact a provider, reserve or book') bounds it against siblings without naming them.

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