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

No annotations are provided, so the description carries the full disclosure burden. It implies a read-only reference lookup via 'posted', but never states whether prices are current or static, whether they are region-specific, or how they relate to the estimated pricing from estimate_job. For a zero-parameter tool the burden is lighter, but the key behavioral trait (static posted list vs computed quote) is left 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 short sentence with no filler, and the core content ('posted installed prices and what they include') is front-loaded. It is efficient but too sparse to be a model of structure.

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?

With no output schema, the description is the only signal about return content, and it does say prices come with their inclusion details. However, it leaves the output shape and the boundary with estimate_job/request_quote undefined, which is the main thing an agent needs to route correctly.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The schema itself confirms an empty object with no inputs.

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 names the resource ('posted installed prices and what they include') which tells an agent what this returns, but it is a noun phrase with no verb and no explicit contrast against sibling estimate_job or get_financing. The distinction between 'posted' prices here and a computed job estimate is implied at best.

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 and no mention of alternatives, despite three plausible siblings (estimate_job, get_financing, request_quote) that overlap in the pricing domain. The agent must infer that this is the lookup-for-list-prices path versus the compute-a-job path.

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