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

No annotations are provided, so the description carries the behavioral burden. 'Retrieve' strongly implies a read-only reference lookup, and the description lists what content is included (deadlines, guarantee, escrow guidance), but it does not explicitly state read-only/non-destructive behavior, permissions, rate limits, or return format.

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 description is a single front-loaded sentence that opens with the verb and resource, then lists the substantive content areas. Every clause adds meaning, and there is 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 zero parameters and no output schema, the description appropriately enumerates the kinds of content returned: appeal ladder levels, deadlines, the Walk-Away Zero Guarantee, and escrow-versus-direct taxpayer guidance. It is complete enough to call, though it does not describe the precise return format or whether the content is static or jurisdiction-specific.

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 has zero input parameters, so there is no parameter surface to document. The baseline for a parameterless tool is 4, and the description does not misrepresent any parameter 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?

The description uses a specific verb, 'Retrieve,' and names the exact resource, the statutory multi-level appeal ladder, while enumerating the levels and included content. It is clearly distinguishable from sibling audit/check/lookup tools that focus on parcel, tax, veteran, or campaign analysis.

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 by the content: an agent can infer this is for appeal-process reference. There is no explicit statement of when to use this versus siblings, no exclusions, and no alternatives named.

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