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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a genuinely useful semantic caveat ('a listed source does not prove nationwide or complete coverage'), but says nothing about pagination limits, page bounds, or result ordering.

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 sentences, front-loaded with the core purpose, followed by the filter/pagination note and the coverage caveat. No filler and every sentence carries 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?

No output schema, but the description characterizes the return payload (coverage plus counts of fresh available non-demo listings) and warns about interpretation. For a simple two-parameter read tool, that is close to complete; only pagination/return-shape specifics are missing.

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 0%, so the description must compensate. It does map both parameters ('supports a state filter and pagination'), but adds no detail on state format (the schema regex handles that), page bounds (max 10000 in schema), or default pagination behavior.

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?

Specific verb+resource: 'Read public land-source coverage and counts of fresh available non-demo listings.' Clearly a coverage/inventory read, distinct from the listing-oriented siblings (search_land, get_land_listing, compare_land_listings). It does not explicitly name or contrast a sibling, so it stops short of 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 — an agent infers this is the source-coverage/inventory read rather than a listing search. There is no explicit when-to-use/when-not or pointer to a sibling like search_land for actual listings.

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