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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses key behaviors: returns a binding USD price, quote_id valid for 15 minutes, no execution occurs, no credits are consumed at quote time, execution through execute_quote consumes prepaid credits, and authentication requires an API key via X-API-Key or Authorization Bearer. This is a thorough disclosure of side effects, validity, and prerequisites for a tool that would otherwise be opaque.

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 but somewhat run-on, with several clauses joined by semicolons and periods. It front-loads the action and product name, then delivers the essential workflow and auth details. While not perfectly structured, every sentence contributes useful information and there is no padding.

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 zero-parameter tool with no output schema, the description is remarkably complete. It explains the returned artifacts (binding USD price, quote_id), the validity period, the absence of side effects, the follow-up execution step, and authentication requirements. An agent has all necessary information to invoke the tool correctly and understand the result.

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 tool has zero parameters and the schema coverage is 100%, so the baseline is 4. The description adds no parameter-specific semantics because none are needed; the empty schema handles this completely. It does mention the product being quoted, which is the only relevant contextual input.

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 states a specific verb ('Request a FREE commercial quote') and a specific resource ('Infrastructure Resilience Score'), and expands with 'Infrastructure climate resilience scoring for critical assets.' This clearly distinguishes it from the many sibling quote_* tools, each of which targets a different assessment type. An agent can identify this tool as the quoting entry point for infrastructure resilience scoring without opening any other description.

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 context for use: it explains that this tool only generates a quote and does not execute, explicitly directing the agent to use 'execute_quote' with the returned quote_id for actual execution. It also notes that execution consumes prepaid credits, implying the quote step is for cost estimation. However, it does not explicitly state when to prefer this over other quote_* siblings, though the unique product name makes that largely implicit. The API key prerequisite is also a helpful usage condition.

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