housecallpro_approve_estimate

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

The description goes beyond the readOnlyHint annotation by disclosing that the tool always refuses, explains why (reCAPTCHA), and what it provides (explanation and link). This is a behavioral trait that is not obvious from annotations alone and is essential for the agent to set correct expectations. No contradiction with the readOnlyHint.

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?

The description is two sentences, front-loaded with the most critical fact (not automatable, always refuses). It is concise with zero fluff. Every sentence earns its place: the first states the refusal, the second tells the agent what to use it for.

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 tool whose sole purpose is to refuse and redirect to a browser, the description covers what the agent needs to know: the outcome (refusal), the reason (reCAPTCHA), and the output (explanation and link). No output schema exists, so the description implicitly covers what is returned. The description is complete for an agent to decide whether and how to call it.

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 only 50% (only the 'link' parameter has a description; 'option_ids' is undocumented). The description does not mention parameters at all, so it fails to compensate for the gap. For the 'link' parameter, the schema description is detailed, but the description adds no value beyond that. The 'option_ids' parameter remains unexplained, and the description provides no clues about its purpose.

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 very specific behavior: the tool always refuses approval, provides an explanation, and returns a link for browser use. This clearly distinguishes it from siblings like housecallpro_decline_estimate or housecallpro_get_estimate, which perform different actions. The verb 'refuses' and the resource 'estimate' are explicit.

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 tells the agent to use this tool to get the explanation and link for browser approval, implying it is not for actual approval. It does not explicitly state when not to use it or mention alternatives, but the context (non-automatable, always refuses) makes the intended usage clear. A small gap: it doesn't say 'use housecallpro_get_estimate for reading estimates' or similar, but the purpose is unambiguous.

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