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

The annotation already declares destructiveHint=true, so the write/mutation profile is covered. The description adds the API endpoint (POST /estimates) and confirms pricing units, but does not disclose side effects such as whether the customer is notified, what the created estimate state is, or auth/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?

Three tight sentences, front-loaded with the core action, then address handling, then the API reference. The final 'Housecall Pro: POST /estimates.' line is largely metadata but cheap; nothing is padded.

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 12-parameter, nested-object tool with no output schema and a destructive hint, the description conveys the essential conceptual model (customer -> options -> line items) but omits scheduling, notification behavior, and most optional-parameter meaning. Adequate but with clear gaps given the tool's complexity.

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 coverage is 67%, below the 80% threshold, so the description must compensate. It clarifies the address_id-versus-new-address choice and the cents pricing convention, but says nothing about the many other params (schedule, notify_customer, lead_source, business_unit_id, assigned_employee_ids), leaving the gaps unfilled.

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 names a specific verb and resource ('Create an estimate for a customer') and adds concrete domain detail (options like Good/Better/Best, line items priced in cents) that clearly separates it from create_job or create_lead. It stops short of naming any sibling as an alternative, so sibling differentiation is implied by the resource rather than stated.

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 only guidance offered is parameter-level ('Give an existing address_id or a new address'), not tool-selection guidance. It never says when to use create_estimate versus create_job, create_lead, or create_customer, nor any prerequisites for creating an estimate.

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