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

Annotations supply only destructiveHint=true, so the description carries most of the burden. It adds the cents pricing convention and the address_id-vs-address choice, plus the API endpoint, but says nothing about side effects such as notifying the customer, permission requirements, or what happens on duplicate estimate numbers beyond the schema note. Adequate additions, but far from rich.

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 short sentences, front-loaded with the core action and payload shape, with no wasted prose. The trailing 'Housecall Pro: POST /estimates' is mildly redundant with the tool name but provides endpoint traceability.

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 mutation with nested objects and no output schema, the description orients the agent on the main payload but never says what the call returns (e.g. the new estimate id) or that a created estimate can be retrieved via housecall_get_estimate. It is workable but leaves a chaining gap.

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?

At 67% schema description coverage, the baseline is 3. The description usefully clarifies unit conventions (cents) and the mutually exclusive address inputs, but several of the 12 parameters (business_unit_id, lead_source, assigned_employee_ids, note, address subfields) remain undocumented in both the schema and the description.

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 ('Create an estimate for a customer') and even describes the internal shape of the payload (options with line items priced in cents), which distinguishes it from sibling create tools like create_job and create_lead. It never explicitly contrasts itself with those siblings, so it falls short of a 5.

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 gives one useful selection rule ('Give an existing address_id or a new address') and a cross-tool pointer ('job_type_id ... From housecall_list_job_types'), which is real routing guidance. But there is no when-to-use vs create_job/create_lead/create_lead guidance, no prerequisites, and no exclusions, so usage is only implied.

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