housecallpro_approve_estimate

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

Beyond the readOnlyHint annotation, the description discloses that the tool always refuses, explains the reCAPTCHA barrier, and states it returns an explanation and a link. This gives the agent accurate expectations about what the tool can and cannot do.

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 sentences deliver the critical limitation, the reason behind it, and the intended fallback usage. The most important information is front-loaded and every sentence earns its place.

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?

The description tells the agent what the tool does, why it behaves that way, and what it returns. With no output schema, the promised 'explanation and link' is sufficient for this narrowly scoped tool, though it never clarifies the role of `option_ids` or the exact response shape.

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 schema documents the `link` parameter in detail, but the tool-level description adds no parameter guidance. The `option_ids` parameter has no description in the schema, and this description does not compensate for that gap, leaving its purpose ambiguous.

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 states a specific behavior—this tool always refuses to approve and instead returns an explanation and a browser link. It clearly differentiates itself from the implied action in the tool name and from siblings like housecallpro_decline_estimate and housecallpro_get_estimate.

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 explicitly says 'Use this to get the explanation and the link to approve in a browser,' giving a clear use case. It also explains why automated approval is not viable, but it does not explicitly contrast with sibling tools or state when not to use it.

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