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 the binding USD price, the 15-minute validity of quote_id, absence of execution/credit consumption, credit consumption on execution, and the required API key authentication. It does not mention rate limits or error behavior, but the key behavioral traits are well covered.

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 every sentence adds value: purpose, output/validity, workflow, and authentication. It loses a point for somewhat clumsy formatting, particularly the missing punctuation before 'Returns' and the run-on flow between the product name and the sentence about the risk score.

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 and no annotations, the description is largely complete: it covers the return value, validity, credit behavior, next-step tool, and auth requirements. The main gap is that it references a location input without explaining how to provide it, which is significant given the empty input schema.

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 input schema has zero documented parameters, so the baseline is 4. The description adds that the quote is 'for a location,' which is meaningful context, but it does not specify how the location should be supplied given the empty schema and additionalProperties: true. This is a minor gap, not a major one.

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 identifies the action ('Request a FREE commercial quote') and the specific resource ('Seismic Risk Score'), and explains the product is a seismic activity risk score for a location. It does not explicitly differentiate itself among the many sibling quote_* tools, but the resource name and scope make the purpose unambiguous.

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 states when to use this tool versus execute_quote: this tool only returns a quote, and execute_quote must be used to run it. It also clarifies that no execution happens and no credits are consumed at quote time, giving clear context for the quote-vs-execute workflow.

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