housecallpro_decline_estimate

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

The description adds important behavioral context beyond the annotations: it is a no-op without confirm:true, makes no network call in dry-run mode, tells the contractor the user is not proceeding, and cannot be undone. The readOnlyHint:false annotation aligns with the stated irreversibility.

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?

Two tightly written sentences lead with the action, then the critical safe-dry-run detail, then the consequential irreversibility. Every sentence earns its place with no fluff or repetition.

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 three-parameter tool with full schema coverage, the description supplies the essential behavioral nuances: confirmation requirement, dry-run preview, no network call without confirmation, and irreversibility. Nothing critical is missing for an agent to invoke it correctly.

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 already documents all three parameters with meaningful descriptions, including the confirm requirement and option_ids source. The description reinforces the confirm semantics and irreversibility but does not add significant new meaning beyond the 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 uses a specific verb ('Decline') with a clear resource ('one or more options on an estimate') and scope. It clearly differentiates from siblings like housecallpro_approve_estimate and read-oriented tools.

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 required confirm:true flow and the dry-run behavior without confirmation, which tells the agent the key precondition for actually executing. It does not explicitly name alternatives or exclusion conditions, but the destructive irreversible nature is clearly conveyed.

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