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

No annotations are provided, so the description carries the full behavioral burden. It implies a computation returning an installed price but does not state whether this is read-only, whether it creates or persists anything, or how it relates to the separate request_quote action. For a tool with zero annotation coverage this is a notable gap.

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?

One short sentence with the key concept front-loaded and no padding. It is a grammatical fragment rather than a full clause, but nothing is wasted.

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 one-parameter tool this is close to adequate, but the description promises 'with the financing option' while the schema exposes only 'zones' and no financing parameter, leaving ambiguity about what the estimate includes. It also never hints at the shape of the returned price (single number, range, breakdown).

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?

With a single parameter at 100% schema coverage, the schema already documents 'zones' including its range. The description's '(indoor units)' gloss matches the schema description and adds no new format or constraint information, so the baseline 3 applies.

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 output (installed price) driven by a specific input (number of zones / indoor units), and the title supplies the verb 'Estimate' for a job. It is reasonably distinct from get_pricing and request_quote, though the mention of 'financing option' blurs the line with get_financing.

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?

There is no guidance on when to use estimate_job versus the sibling tools get_pricing, get_financing, or request_quote, nor any stated prerequisites. The agent must infer the routing entirely from tool names.

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