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

With no annotations, the description carries the full burden and does decently: 'Replaces' signals a destructive overwrite of existing grounds, plus it discloses the credential requirement (token), cost (Free), and a hard 48-hour deadline. It omits reversibility and any response/confirmation detail, keeping it from a 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?

Compact and front-loaded, with the purpose first and constraints/metadata trailing. The lead-in 'I want to...' reads like a sample user utterance and is slightly wasteful, but everything else earns its place.

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 mutation tool with no annotations and no output schema, the description covers the essentials: what changes, the credential, the deadline, cost, and governing rule. Nothing critical to correct invocation is missing, though it could say more about the replacement semantics.

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. It maps each of the three parameters at a high level ('the appeal's reference' for ref, 'Credential: token' for token, grounds implied), but adds no format, length, or content guidance beyond the bare minimum.

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?

States a specific verb+resource: 'change the grounds of my grave-wrongs appeal' and clarifies 'Replaces your grounds of appeal.' An agent can distinguish this from siblings like extend_grave_wrongs_time or appeal_grave_wrongs_finding. It does not explicitly name a neighbor, so it falls short of a 5.

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?

Provides a real constraint ('within 48 hours of the notice') and points to the appeal's reference, but names no alternative tool and no when-not-to-use condition. Usage is implied through the timing window rather than explicit routing.

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