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

With no annotations provided, the description carries full behavioral disclosure responsibility. It covers key traits: the quote is binding, the price is in USD, the quote_id is valid for 15 minutes, no execution happens, no credits are consumed, and an API key is required. This goes well beyond a minimal statement of the tool's existence.

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 a single compact paragraph where every sentence earns its place: the action and resource are front-loaded, followed by scope, return value, validity, execution path, cost implications, and authentication. There is 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 are zero parameters and no output schema, the description fully covers what the tool returns, how long the quote remains valid, what the next step is (execute_quote), and what credentials are required. Nothing needed for a correct call 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 input schema has zero parameters, so the baseline is 4. The description correctly avoids inventing parameter details; instead it describes the output (binding USD price and quote_id) and the required authentication method, which is the only invocation-level information an agent needs here.

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 opens with a clear imperative 'Request a FREE commercial quote for: Environmental Due Diligence', naming the exact verb and resource. It then adds context ('for mergers, acquisitions, and investments') that distinguishes this quote tool from the many other quote_* siblings, even without an explicit comparison.

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?

It explicitly states that this tool only requests a quote and should not be used for execution, then directs the agent to the correct alternative: 'Use execute_quote with the quote_id to run it'. It also clarifies the cost model (no credits consumed now, execution consumes prepaid credits), making when-to-use versus when-not-to-use unambiguous.

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