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

The description contradicts the annotations: it presents the tool as a pure information-returning operation while annotations mark it as destructiveHint=true and readOnlyHint=false. No additional behavioral context is provided to reconcile this discrepancy.

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?

Three sentences, front-loaded with purpose, and packed with specific useful details (labor rates, factors, market data). No redundant or wasteful text.

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?

While the description is thorough about the output content, the annotation contradiction leaves critical behavioral ambiguity unresolved. The absence of any mention of potential destructive side effects or non-read-only behavior makes it incomplete for safe agent invocation.

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 covers 100% of parameters, so baseline is 3. The description adds context about factors affecting cost but does not specifically elaborate on how to provide 'severity' or 'damage_type' beyond the schema's generic descriptions.

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 begins with a specific verb 'Returns' and identifies the resource 'Philadelphia-area restoration cost estimates' broken down by service type, clearly distinguishing it from sibling tools like assess_damage or check_insurance_coverage.

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 when to use it (when needing cost estimates) but lacks explicit alternatives or exclusions. It details included factors, aiding an agent's decision, but no direct comparison with sibling tools is provided.

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