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

With no annotations, the description carries the full burden and does substantial work: free cost, 72-hour window, three-judge panel none of whom sat below, unanimity requirement, and the key reassurance that nothing enters the record and no credential is withdrawn until the appeal is decided. It does not state what the outcome/return looks like or failure modes, keeping it below 5.

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?

Purpose is front-loaded and most sentences earn their place (timing, panel composition, non-entry to record, amendment window). The trailing 'Credential/Cost/Source' metadata is compact, though the in-character prose makes it slightly denser than needed.

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 no-annotation, no-output-schema process tool it covers behavior well, but leaves the meaning of 'ref' and the outcome of a successful appeal undefined. An agent knows the rights and windows but not exactly what it must supply or will receive.

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 define all three params. It clarifies token ('Credential: token') and grounds (via the amendment sentence), but leaves 'ref' — the required identifier — entirely unexplained, and gives no format for token or grounds beyond maxLength already in the schema.

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 act (appealing a grave-wrongs finding to three fresh judges) and its distinguishing feature ('Appeals as of right'), which separates it from siblings like seek_leave_to_appeal. It never explicitly names those siblings, but the verb+resource+scope is 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?

It gives clear triggering context — 'within 72 hours of service of the finding' and 'as of right' — plus a related window ('amend your grounds for 48 hours') that routes toward amend_grave_wrongs_grounds. It lacks an explicit 'use X instead when...' exclusion, 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.