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

With no annotations provided, the description carries the full burden and covers key behaviors: it returns a binding USD price and quote_id valid for 15 minutes, does not execute or consume credits, and requires an API key. It also notes the quote is free. This is comprehensive disclosure for a quote-request tool.

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 concise and well-structured: it starts with the core purpose, then adds essential details (return, validity, no execution, credits, API key, next step). Each sentence adds value, and the most critical information is front-loaded.

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 and no output schema, the description provides all necessary context: what it does, what it returns, how long the quote is valid, that it doesn't consume credits, the API key requirement, and how to proceed. Nothing an agent needs to call it correctly is missing.

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, so there are no semantics to explain. The schema already covers this (empty object with additionalProperties true). The description adds no parameter info, which is appropriate given the absence of parameters. Baseline for 0 params is 4.

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 explicitly states the action: 'Request a FREE commercial quote for: Carbon Assessment.' It clearly identifies the resource (carbon assessment) and the operation (requesting a quote), distinguishing it from execution via execute_quote and from other assessment-specific quote tools by naming the exact type.

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 assessment, and clarifies that this tool does not execute anything. It implies this is the correct tool for carbon assessment quotes, but it doesn't explicitly exclude using other quote_* tools for other assessment types. The guidance is clear for the intended flow.

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