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

With no annotations, the description does carry some burden and delivers: it discloses the auth requirement (api_key or Authorization: Bearer), the paid-tier context, the state-wide fallback behavior, and the response shape. It says nothing about error behavior, ambiguous legal descriptions, or accuracy/partial-match handling, which matters for a geocoding tool with free-form input.

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?

The body is dense and earns its space — the input examples and return-shape summary are high value. However, the lead is a commercial/billing sentence rather than the purpose, so the definition is not front-loaded and the agent has to read past pricing tiers before learning what the tool does.

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?

An output schema exists, so return values needn't be spelled out, yet the description still summarizes them. The real gaps are positional: no differentiation from plss_lookup and no guidance on what to do when a legal description resolves ambiguously across states or matches multiple sections.

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 0%, so the description must compensate, and it largely does: `q` gets four concrete format examples (plain, fractional section, written-out township, BLM-coded), `state` is explained as a two-letter code with a stated empty-default behavior, and `api_key` is tied to the account and the Bearer alternative. Only the exact expected string format for `state` (case, validation) is left implicit.

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 core purpose is inferable from the fragment 'a legal description → where it is', i.e. resolving a PLSS legal description to a location, but there is no explicit verb+resource statement and the opening is a billing blurb rather than a purpose statement. It also fails to differentiate itself from the sibling plss_lookup, which appears to be a very close alternative.

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?

There is no explicit when-to-use or when-not-to-use guidance, and the obvious alternative, plss_lookup, is never named. The only usage-adjacent hints are the `state` fallback behavior ('tried in every PLSS state when empty') and the accepted `q` formats, which tell the agent how to call it but not when.

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