hazard.score

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

No annotations provided, so description carries full burden. It discloses coverage varies by hazard and geographic region, references the API endpoint, and implies read-only behavior. Lacking explicit statement that it does not modify data.

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?

Front-loaded with purpose, then usage, then coverage notes. Single paragraph is efficient but could be slightly more concise; still highly informative.

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?

Given no output schema, description explains sub-scores and sources sufficiently for selection. Coverage details help set expectations. Lacks output structure but acceptable for this tool type.

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 covers 100% of parameters, but description adds value: explains parcel_id format (composite from parcel.lookup) and that include is a subset filter. Reinforces and clarifies beyond schema.

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 clearly states it provides a composite hazard score for a parcel, listing specific hazards (flood, wildfire, seismic, etc.) with sources. It distinguishes from sibling tool parcel.compare for multiple parcels.

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?

Explicitly says when to use (property risk profile, insurance pricing) and when not to (comparing multiple parcels, suggesting parcel.compare). Also mentions coverage variations by region.

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