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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely new behavioral context: the output is an approximate file-by date rather than an authoritative deadline, and the user should verify against their own notice - an important caveat not captured anywhere else.

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?

Front-loaded with the purpose and then the example phrasings, with zero filler. The opening 'Appeal My Claim. How long someone has to appeal...' partially duplicates the title, a minor redundancy.

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?

No output schema exists, so the description carries the return-value burden; it does this by describing the approximate file-by date and the verification caveat. Combined with full schema coverage and complete annotations, an agent has what it needs, though the output format itself remains somewhat unspecified.

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%, with each parameter documented in the schema itself (including the enum on urgent). The description only alludes to denial_date ("with the date on the denial notice") and adds nothing about urgent or plan_type, so baseline 3 is appropriate.

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 states a specific informational purpose - how long someone has to appeal and how fast the plan must decide - with concrete example user phrasings. It is distinguishable from siblings like get_appeal_rights and draft_appeal_letter, though it never states an explicit verb for what the tool returns.

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?

It gives clear triggering questions ("how long do I have to appeal?", "when is my appeal due?") and the condition for usefulness (have the denial date handy). It does not explicitly name sibling alternatives such as get_appeal_rights for the 'when/not-this-tool' case, so it stops short of a 5.

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