Get Estimate

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

There are no annotations provided, so the description carries the full burden of disclosing behavioral traits. It only says 'Get a single estimate by ID' without mentioning return format, error handling, permissions, rate limits, or any side effects. The docs link is a reference but does not enrich the description with behavioral context.

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 one concise sentence that front-loads the core purpose. The docs link is appended without cluttering the main statement. Every word earns its place; there is no redundancy or filler.

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?

This is a simple get-by-ID tool with a single fully documented parameter, but there is no output schema and no annotations. The description does not explain what the response contains (e.g., full estimate object fields) or any edge-case behaviors, which leaves some gaps for the agent. However, for a basic read operation, the description is minimally adequate.

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 already describes the only parameter (estimate_id) as 'Housecall Pro estimate ID' with 100% coverage, so the description adds no additional semantic value beyond that. The description's mention of 'by ID' reiterates what the schema provides, meeting the baseline but not exceeding it.

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 'Get a single estimate by ID' clearly states the action (get), resource (estimate), and scope (single by ID), distinguishing it from list_estimates which would retrieve multiple records, and from create_estimate which creates.

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 provides no guidance on when to use this tool versus alternatives like list_estimates or create_estimate. It does not mention any prerequisites, exclusions, or alternative contexts. The only implied usage is that you must have an ID, but this is not explicitly stated.

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