Create Estimate

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

With no annotations provided, the description carries the transparency burden. It states the core behavior (creation) and directs the user to external docs for field specifics. However, it does not disclose return values, error handling, or side effects beyond the obvious 'create' implication, so it only meets the minimum bar.

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 remarkably concise: two sentences that state the purpose and provide a direct link to authoritative documentation. Every sentence earns its place with no filler or redundancy.

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 with a single parameter and no output schema, the description is quite complete: it tells the agent what to do, where to find the exact fields, and provides a docs link. The only gap is lack of return value info, but the schema and the link to docs compensate sufficiently for an agent to proceed.

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 provides a thorough description of the 'body' parameter, including that it is a raw JSON request body, matches Housecall Pro's docs, and is passed straight through. The tool description merely repeats the need to match fields, adding no new conceptual information beyond what the schema covers, so the baseline of 3 is appropriate.

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 explicitly states 'Create a new estimate', which is a specific verb+resource combination. This clearly distinguishes it from siblings like get_estimate and list_estimates, leaving no ambiguity about what action it performs.

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 phrase 'Create a new estimate' clearly implies when to use this tool: when the agent needs to create an estimate. It does not explicitly list alternatives or exclusion cases, but the purpose is obvious enough that an agent can correctly select it among siblings without further guidance.

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