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

Goes beyond the annotations by disclosing concrete side effects: it creates a customer record and quote request at Detritus and sends the customer a text and/or email, and it warns 'Not safe to retry' because a repeat call duplicates the request. This usefully reinforces the non-idempotent/destructive hints with real-world consequences, though it says nothing about failure modes or permission requirements.

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?

Purpose and the single-request constraint are front-loaded, and the retry warning is placed at the end where it is most salient. The middle sentence enumerating required fields is somewhat redundant against a 100%-covered schema, but overall it is tight and readable.

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 complex nested mutation tool, the description covers the essentials an agent needs: the confirmation gate, the one-job/one-quote rule, duplicate-call risk, external notification side effects, and the returned id (redundant given the output schema). Only error handling and the upstream get_service_availability ordering are left implicit.

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?

Schema description coverage is 100%, so the schema already documents every nested field, enum, and cross-field rule (e.g. disposalMaterial required when dumpsterSize is set). The description mostly restates the required fields (first name, last name, email, phone, address, delivery date, products, customerConfirmed), adding little beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Submit one quote request to Detritus') and scopes the operation (one request per job = one quote). It is unmistakably the only write/submission tool among read-oriented siblings like get_service_availability and check_service_request_status, so an agent can route to it without opening a schema.

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?

Gives clear conditions: all items for one job go in a single request, and customerConfirmed: true is required only after the customer has reviewed the details. It does not explicitly name alternatives or say when NOT to call it (e.g. call get_service_availability first to obtain product ids), though the schema implies that workflow.

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