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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses meaningful behavioral traits: the scoring mechanism (starts at 100 and subtracts deductions), partial geographic coverage for parcel records (Maryland/Harris County only), and failure tolerance ('A failing source is noted, not fatal'). This is rich, useful context.

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 information-dense but well-organized: headline output, data sources, scoring logic, failure behavior, and caveat. Every clause earns its place, though it is slightly long and could be parsed more easily with sentence breaks or lists.

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 complex multi-source tool with no output schema, the description is complete: it covers input alternatives (address vs lat/lon), source coverage, geospatial scope, scoring, partial-failure behavior, and the professional-assessment disclaimer. An agent has enough to invoke it correctly and set expectations.

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%, so the baseline is 3. The description adds some context by noting geocoding accepts an address or lat/lon, and that state can override EPA/parcel/declaration scoping, but this mostly mirrors the schema descriptions rather than adding substantial new meaning.

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 produces a composite site-bound hazard and environmental profile with an explainable 0-100 risk score, and enumerates the exact data sources it fans out to. This distinguishes it from single-source siblings like flood_zone_lookup or earthquake_recent and similar aggregate tools by emphasizing 'one-call' cross-source synthesis.

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 usage context is implied: use this when you need a consolidated multi-source location risk profile, since it 'fans out' to many datasets. However, it never explicitly says when to choose this tool over environmental_site_risk or lane_location_risk_pack, nor does it state any exclusions or prerequisites.

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