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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds real context beyond that: the authoritative data sources (USGS 3DEP 1-meter LiDAR, karst subsidence databases), the impairment thresholds (>25% grade), and the evidentiary deliverable (Board-admissible Exhibit T). It stops short of saying what happens when only address is supplied or how the impairment is quantified in the output.

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?

It is a single front-loaded sentence that leads with the action and data sources and closes with the downstream deliverable, with no wasted wording. The density of domain jargon makes it slightly harder to parse quickly, but nothing is redundant.

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?

There is no output schema, so the description must carry the return-value burden, and it only gestures at the result ('quantify impairments', 'Exhibit T') without saying what metrics, citations, or qualifiers the agent should expect. For an eight-parameter evidentiary audit tool, that leaves a meaningful gap even though the data sources and thresholds are well stated.

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 all eight parameters, including the format choice for 'html' Exhibit T output, are already documented in the schema. The description reinforces the purpose of the Exhibit T artifact but adds no syntax, format, or constraint detail beyond what the schema provides, so it sits at the baseline.

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 and resource (audit a parcel against USGS 3DEP LiDAR elevation profiles and karst subsidence databases) and states the concrete measure produced (steep slope >25% grade, sinkhole impairment) plus its downstream use (adverse topography adjustment, Exhibit T). It does not explicitly distinguish itself from the sibling audit tools, which is the only thing keeping it off a 5.

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?

Usage is only implied: the agent can infer this is the tool for topography-based valuation appeals, but there is no statement of when to prefer it over another audit or what preconditions must hold (for example, whether coordinates are required or whether the address alone is sufficient for the 3DEP lookup).

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