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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds genuine value beyond them: it discloses the response shape (total count plus a distance-sorted page) and an important data caveat that geometry is the recorded PLSS land description, not the staked boundary.

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?

Two sentences, front-loaded with the scope, and the second sentence's return-field list is justified because there is no output schema. Slightly dense, but no filler.

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?

With 7 parameters and no output schema, the description carries the return-value burden and does so well (count, fields, sort order, geometry caveat). Pagination and filter semantics live in the schema. The remaining gap is routing guidance against the other blm_* siblings.

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 schema already documents limit, status, radius_km, claim_type, coordinates and the paging cursor. The description restates some of this (claim type/status fields, distance sorting) but adds no syntax or format detail beyond the schema; 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+resource+scope: 'US federal mining claims (BLM MLRS) within a radius of a latitude/longitude'. The radius framing lets an agent tell it apart from the sibling blm_claims_in_bbox (bounding box) and blm_claims_case (single case) without opening any schema.

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 through examples ('claims staked around a lithium, gold or uranium deposit in Nevada, Arizona, Utah, Wyoming'). It never states when to prefer this over blm_claims_in_bbox or blm_claims_summary, nor 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.