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

With no annotations provided, the description carries the full burden and does so excellently. It discloses that the tool returns a binding USD price and a quote_id valid for 15 minutes, that no execution occurs and no credits are consumed, that execution requires the execute_quote step, and that an API key is required (X-API-Key or Authorization: Bearer). This fully informs the agent of the tool's behavior, side effects, and authentication needs.

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 information-dense but well-structured. It starts with the core purpose, then details the response, validity, next steps, and authentication. Each sentence adds value; there is no filler. Slightly verbose but every clause is essential, so it earns a 4.

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 no-parameter quote tool, the description is comprehensive. It explains what the response contains (binding price, quote_id), the validity window, that no execution happens, that a follow-up tool is needed, and authentication requirements. Nothing an agent needs to call the tool 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 input schema has zero parameters, so the baseline is 4. The description does not need to explain parameters since there are none. It implicitly notes that the request is for a quote on industrial emission detection, which is sufficient. No additional parameter information is required.

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 verb ('Request a FREE commercial quote'), the resource ('Industrial Emission Detection'), and the specific function ('Detect unauthorized industrial emissions using thermal satellite data'). It clearly differentiates from sibling quote tools by naming its unique domain, making it easy for an agent to select the correct one.

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 explains the workflow: this tool only generates a quote, not execution, and directs the agent to use 'execute_quote' with the returned quote_id for actual execution. It also clarifies that no credits are consumed at this stage. While it doesn't explicitly compare to other quote tools, the domain-specific purpose and next-step guidance provide clear context for when to use it.

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