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

With no annotations, the description carries the full burden and does an excellent job: it states the quote is free, returns a binding price and quote_id valid for 15 minutes, does not execute, does not consume credits, and requires an API key. It also explains that execution via execute_quote consumes prepaid credits. This fully discloses the tool's behavior.

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 concise sentences that front-load the purpose and then provide essential workflow and auth details. Slightly more verbose than strictly necessary but all information is relevant and well-ordered.

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 tool with no parameters, no output schema, and no annotations, the description covers everything an agent needs: what it returns, the validity window, the next step, the auth requirement, and that it does not execute. It is fully self-contained.

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 has zero parameters, so there is nothing for the description to explain. Baseline for 0 params is 4; the description adds no parameter-specific details because none exist, which is appropriate.

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 (request a quote) and resource (Drought Assessment), and explicitly names what it returns (price and quote_id). The description also notes it covers severity and duration assessment, which clearly differentiates it from sibling quote_* tools.

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 clearly explains the workflow (quote then execute via execute_quote) but does not provide explicit guidance on when to choose this tool over its many siblings. It implies usage by naming the assessment type, but lacks direct alternatives or exclusion criteria.

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