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

With no annotations, the description carries the full burden. It transparently discloses the payment mechanism (x402, USDC, cost ~$0.20/call), that no account or API key is needed, and that it returns JSON with specified fields. It does not mention any side effects, but the operation is likely read-only and non-destructive, which is implicit.

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 description is two sentences and efficiently conveys payment details, data sources, and output format without unnecessary words. The first sentence is slightly dense but still clear and front-loaded with essential information.

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?

Despite no output schema, the description lists all returned JSON fields (ok, pga_percent_g, etc.) and names the data sources. It does not explain coordinate system or units, but for a multi-source hazard indicator, it covers the main expectations adequately.

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 has 0% description coverage for the two parameters (lat, lon). The tool description does not add any meaning beyond the schema's type information (number). It fails to specify units (e.g., decimal degrees) or any constraints, which is inadequate given the lack of schema 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 clearly states the tool's function as a 'Multi-source US property hazard indicator' combining USGS seismic, FEMA disaster history, and NOAA active alerts. It distinguishes itself from the sibling tool 'assess_property_hazard' by noting 'same underlying data' and the x402 payment method, making the purpose and differentiation explicit.

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 provides context for when to use this tool: when the agent needs to pay directly on-chain without a GISGP account or API key. It notes that it has the same underlying data as 'assess_property_hazard', implying an alternative for payment preferences, but does not include explicit when-not or exclusions.

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