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

With no annotations, the description carries the full burden, and it covers several important behaviors: returns a binding USD price, a quote_id valid for 15 minutes, no execution, no credit consumption, and requires an API key (X-API-Key or Authorization: Bearer). It also clarifies that execution consumes prepaid credits. It does not mention rate limits, quote expiration handling, or failure modes, but for a quoting tool these are minor omissions.

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 three sentences and front-loaded with the primary purpose, followed by the definition, return behavior, execution guidance, and authentication requirements. Every sentence adds distinct information. Minor formatting issues (a sentence fragment after the colon and a missing period after "15 min") keep it from being a perfect 5.

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, no-output-schema tool, the description covers the entire workflow: request a quote, receive a binding price and quote_id, execute later via execute_quote, and note the credit and auth implications. It could mention what happens when the 15-minute validity expires, but this is a minor gap given the tool's simplicity and the presence of sibling tools like get_runtime_status for follow-up.

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 reinforces this by focusing on the quoting flow rather than parameters. It adds value by explaining what will be returned (a binding USD price and quote_id) and how the quote_id should be used with execute_quote, which is useful semantic context beyond the empty schema.

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 specific verb and object: "Request a FREE commercial quote for: Biodiversity Assessment," and then defines what that assessment involves ("Biodiversity evaluation using multi-source ecological data"). It distinguishes itself from the sibling execute_quote by stating it returns only a quote_id and does not execute. The many sibling quote_* tools are differentiated by their assessment type, and this description adds a clear definition of the biodiversity assessment itself.

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 explains when to use this tool vs. execute_quote: "no execution yet and no credits consumed" and "Use execute_quote with the quote_id to run it". This gives an explicit next step and a key exclusion (this tool does not run the job). It does not explicitly contrast with other quote_* tools, but the assessment type is evident from the tool name and the defining phrase, so the guidance is sufficient.

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