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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world behavior, so the description adds real value beyond them: the explicit 'unavailable' outcome when no verified package exists, and the warning that CAD compatibility and the current tax year are not assumed, which tells the agent not to infer unverified facts. It stops short of describing response shape or field-level reliability.

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 tight sentences with the core purpose front-loaded and the failure mode immediately after. The closing sentence is dense jargon ('CAD compatibility') that isn't explained, which costs a little clarity but no words are wasted.

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?

No output schema exists, and the description does name the main return facets (verified details, source coverage, missing facts, limits) plus the empty-result case. It could say more about the response structure, but for a two-parameter read tool with full annotations it is nearly sufficient.

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%, with both state (two-letter code, example TN/GA) and county (name or five-digit FIPS) already documented in the schema. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

States a specific verb ('Read') and a specific resource (a county records package's verified details), then enumerates what the payload contains: source coverage, missing facts, and limits. That resource is clearly distinct from sibling tools like gisdb_search_records or gisdb_get_search, which operate on searches rather than county packages.

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 context is only implied by the note that it returns 'unavailable' when no verified package exists, which hints at a pre-flight confidence check. It never says when to call this versus gisdb_search_records or gisdb_get_search, and gives no prerequisites or exclusions.

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