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

With no annotations provided, the description carries the full burden, and it does so well. It discloses authentication requirements, that the quote is binding and valid for 15 minutes, that no credits are consumed at quote time, and that execution via execute_quote consumes credits. This goes well beyond basic purpose disclosure.

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 appropriately short and front-loaded with the core purpose. It packs in quote validity, credit behavior, downstream execution, and auth requirements without excessive wording. Minor formatting/gap issues ('network Returns' and the missing punctuation) prevent a perfect 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, the description is remarkably complete. It covers what the tool returns, how long the quote_id is valid, what the quote does not do, what the next step is, and what authentication is required. Nothing essential is left for the agent to infer.

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 is an empty object, so there are no parameter semantics to explain. The baseline for a zero-parameter tool is 4, and the description does not need to compensate for missing schema documentation.

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 uses a specific verb ('Request a FREE commercial quote') and a specific resource ('Supply Chain Climate Risk'), and further clarifies it is a 'Climate risk assessment across a supply chain network'. This clearly separates it from the many sibling quote_* tools because it names the exact assessment domain.

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 states that this tool only obtains a quote, does not execute anything, and that execute_quote should be used afterward with the returned quote_id. It also clarifies that execution consumes prepaid credits, helping an agent decide whether to invoke this tool now or later. It does not explicitly compare against alternative quote_* tools, which keeps it just below a 5.

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