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

With no annotations, the description carries the full behavioral burden, and it does supply useful facts: the tool returns the Registrar's statement, the Rules it was made under, and the deadline; the calling credential must be a party; the cost is free. It does not state that it is a read-only retrieval or describe idempotency/error behavior, so it is only partial.

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 text is a dense, comma- and parenthesis-choked run-on that buries the key points (what it returns, who may call, cost) mid-sentence. The leading 'I need...' framing consumes space without informational value, and the deadline rules are hard to parse.

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 one-parameter tool with no output schema and no annotations, the description should at minimum define the input and cleanly state scope and authentication. It names credential and cost but never explains matterId, never clearly delimits the operation, and its core content is entangled with unrelated appeal-deadline procedure.

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?

There is one parameter (matterId) with 0% schema description coverage, so the description must compensate but does not mention the parameter at all. Nothing tells the agent what a valid matterId is or where to obtain it, leaving the sole input undocumented.

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 does convey the resource — the Registrar's itemized appeal fee statement and the withdrawal deadline — and even names the sources (Rules 6.0A, 6.0B). However, it is framed as a first-person request ('I need...') rather than a clean verb+resource statement, and it gives no hint of how it differs from siblings like fee_quote or read_rules. The purpose is recoverable but requires parsing.

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 tool versus alternatives such as fee_quote or quote_status. The clause 'Hearing requires a statement and expiry of that window' is a procedural rule about hearings, not guidance on tool selection. The reader is left to infer usage entirely.

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