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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds genuinely useful behavioral context beyond them by enumerating what comes back – claim metadata, PLSS legal description, mapping quality/confidence, and bounding box – which matters because there is no output schema.

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?

One long but front-loaded sentence; the lookup key and both identifier forms precede the field enumeration, and there is no filler. Slightly dense as a single sentence, but every clause 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?

For a one-parameter lookup with no output schema, the description compensates well by listing the returned fields. Minor gaps remain: it does not say what happens when a serial is not found (error vs empty result) or whether records are authoritative/current.

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 coverage is 100% and the single case_id parameter's schema description already states the MLRS and legacy serial formats with identical examples. The description repeats this dual-format guidance rather than extending it, 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+resource (retrieve one BLM mining claim) keyed by case serial number, and the 'One ... by case serial number' framing cleanly separates it from the spatial siblings blm_claims_in_bbox, blm_claims_near, and the aggregate blm_claims_summary. Examples of both serial formats make the resource unambiguous.

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 implied rather than stated: the agent can infer this is the direct-lookup path when it already holds a serial number, versus the bbox/near siblings for spatial queries. No explicit when-to-use, when-not-to-use, or named alternative is given, so the routing decision is left to inference.

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