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

With no annotations, the description carries the full behavioral burden, yet it does not say whether the result covers all states or a subset, whether the data is static reference content, or how large the response is. It does imply a read-only reference lookup, which is the only behavioral signal present.

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?

A single compact phrase with no filler, and the key scope qualifier ('per-state') is front-loaded. It is slightly too terse to function as a sentence, but nothing is 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?

For a zero-parameter reference tool with no output schema, the description should at least indicate coverage (all states?) and the shape of the returned rules. It signals the subject matter adequately but leaves the agent guessing about scope and return structure.

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?

The tool takes zero parameters, so there is nothing for the description to clarify beyond what the empty schema already conveys. Baseline 4 applies; the description correctly implies a parameterless, return-everything lookup.

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 description names the resource and its content areas (mechanism, redemption period, statute) on a per-state basis, so an agent can guess it returns reference data. But it is a bare noun phrase with no verb and no differentiation from siblings like list_states or search_records, leaving the agent to infer that this is a static lookup rather than a search.

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 statement of when to call this versus list_states, search_records, or data_sources, and no prerequisites or exclusions. The agent must infer usage entirely from the phrase 'per-state tax-sale mechanism'.

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