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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds that the result is a cost range plus contractor guidance, which is genuinely useful since no output schema exists. It omits the area bounds (500-8000 sq ft) and the fact that pitch/tearoff/material are optional, which would have helped set expectations.

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?

Two sentences, no filler, and the trigger condition is front-loaded ahead of the input/output summary. Every clause earns its place.

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 correctly compensates by naming the return (cost range and contractor guidance), and annotations cover the safety profile. It is nearly complete, missing only a note on which parameters are optional and the area limits.

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?

Schema description coverage is 100% with enums documented for pitch, tearoff, and material, so the schema already carries parameter meaning. The description only restates area, pitch, and material and omits tearoff entirely, adding no syntax or semantics beyond the schema. 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?

States a specific resource (roof cost) with concrete scope variants (new roof, replacement, repair) and names the inputs (area, pitch, material). The domain word 'roof' separates it from the electrical/hvac/plumbing/solar/water-heater siblings, but it never explicitly acknowledges or routes away from those alternatives.

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?

'Use when a user asks what a new roof, roof replacement, or roof repair will cost' is an explicit, well-scoped trigger condition that tells the agent exactly which user intent selects this tool. It gives no when-not condition or guidance on choosing between this and other cost calculators.

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