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

No annotations are provided, so the description carries the full burden. It does disclose a meaningful trait — prices are 'quoted as written', i.e. unnormalized verbatim figures from contractor sites — which warns the agent not to expect canonical or comparable pricing. However it says nothing about coverage, freshness, or how results are returned, leaving the read-safety and result-shape profile unstated.

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?

A single tight sentence with no filler and the key scoping qualifiers (installed, Austin-area, contractor-published) front-loaded. It is efficient, though the terseness leaves the action verb implicit.

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 zero-parameter read tool with no output schema and no annotations, the description is minimally adequate: it defines the data but does not describe the return structure, how many benchmarks to expect, or freshness. With no output schema to lean on, slightly more disclosure would be warranted.

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 has zero parameters, so per the baseline there is nothing for the description to document. The sentence about sourcing adds interpretive context rather than parameter detail, which is appropriate for a no-arg lookup.

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 identifies the resource precisely (installed HVAC prices from Austin-area contractors' own websites) but never states the action the tool performs — no verb like 'returns' or 'list'. An agent can infer it retrieves price data, but the purpose is implied rather than stated, and the distinction from siblings like search_companies rests only on the topic noun.

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 when-to-use guidance, no condition that selects this tool over search_companies or request_mini_split_quote, and no exclusions. The description is purely a data definition with no routing signal.

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