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

With no annotations, the description carries the full burden of revealing behavior. It discloses that a binding USD price and quote_id are returned (valid 15 min), that no execution occurs and no credits are consumed, that execution requires prepaid credits, and that an API key is mandatory. This is comprehensive for a quote tool and leaves little ambiguity about side effects or prerequisites.

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 compact and front-loaded: it opens with the purpose, then each sentence adds a distinct piece of essential information (product scope, return value, validity, next step, auth). No filler or redundancy.

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?

Given there is no output schema, the description adequately covers the key return items (price, quote_id, validity) and the follow-up action. It also mentions auth and credit implications. It's sufficient for correct invocation, though it doesn't specify error conditions or the exact response structure beyond the two key fields.

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 the baseline is 4. The description adds no parameter-specific details, but there are none to document. It does not need to compensate for schema gaps because the schema is trivially complete with no properties.

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 clearly states the tool's purpose: requesting a FREE commercial quote for Water Scarcity Forecast. It specifies the resource ('Water Scarcity Forecast'), the action ('Request a quote'), and the product details (12-month forecast, climate models), which distinguishes it from the many 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 explicitly tells the agent to use execute_quote with the returned quote_id to run the forecast, providing clear next-step guidance. It also clarifies that this tool does not execute or consume credits, implying when to use it (before execution). However, it does not directly contrast with other quote_* tools or state when this specific forecast is preferred over alternatives.

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