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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context about calculation scenarios (optional shingle allowance, historical asphalt installation and removal, standing-seam bid endpoints, benchmark subtotal) and a limitation around missing local prices.

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 first sentence is front-loaded and clear, but the second sentence is a long, somewhat malformed run-on ending in 'missing local prices remain get a local quote.' The content could be tighter and better structured.

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 moderately complex calculator with no output schema, the description lists the main calculated outputs and scenarios, and it notes the local-price limitation. It is largely complete, though it could clarify what the result object contains or how to interpret the benchmark subtotal.

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 high at 88%, so the schema already documents most parameters. The description references pitch, footprint, waste, material, and quoted extras, but adds little syntax or format detail beyond what the schema provides.

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 a specific verb ('Estimate') and resource ('sloped roof area and roofing squares'), then extends to cost scenarios including asphalt and standing-seam. An agent can distinguish this from generic cost calculators by the roof-specific geometry and material scope.

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 description implies usage from a measured footprint and pitch, and notes that missing local prices require getting a quote. However, it does not explicitly state when to use this tool versus alternatives among the many sibling calculators, nor does it give clear exclusions.

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