housecallpro_healthcheck

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

Annotations already provide readOnlyHint=true, so the description does not need to restate safety. The description adds useful behavioral context by revealing that the tool performs a live reachability check and a customer-link resolution check, and its wording implies external network access consistent with openWorldHint.

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 with no redundancy. The core purpose is stated first and the usage guidance is delivered in a short, imperative second sentence.

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 simple zero-parameter diagnostic tool, the description covers what it checks and when to run it. It does not specify the exact output format, but no output schema exists and the healthcheck's role as a first-line diagnostic is clear.

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 tool has zero parameters and an empty input schema, so the schema places no burden on the description. The baseline for no-parameter tools is 4, and the description appropriately focuses on purpose rather than parameters.

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 ('Check') and names two concrete resources: reachability to Housecall Pro and resolution of a configured customer link. This clearly distinguishes it from sibling data and mutation tools like get_estimate or approve_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?

'Run this first when a tool fails' is an explicit, actionable usage instruction. It tells the agent exactly when to invoke this tool, and no competing diagnostic alternative appears among the sibling tools.

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