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

With no annotations, the description carries the full burden and does so richly: it discloses the credential required (party), the cost-shifting rule (losing party pays measured first-instance cost plus estimated appeal cost plus 30%), and the special agent-time procedure under Rules 0.47+ including fee handling, the two-hour answer window, and the court hearing the appeal of its own motion. The cited rule sources (6.0, 6.0A, 6.1) further ground the behavior.

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 purpose is front-loaded and most content is substantive, but the middle is a dense chain of comma-spliced procedural rules that is hard to parse in one pass. Opening with a first-person party statement rather than a tool-oriented verb is an odd structural choice.

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 seven-parameter mutation tool with nested objects, no annotations, and no output schema, the description covers procedure, deadlines, cost, and credential well, but leaves the roles of disputes, authorities, and argument unaddressed, so an agent cannot fully map inputs to the filing without opening the schema.

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 very low (14%), so the description must compensate. It does explain two parameters well – the defence to include when a default judgment is appealed, and feeAcceptedUpToCents and its effect on the two-hour withdrawal period – but it is silent on argument, disputes, authorities, and matterId, leaving most of the seven parameters 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 frames the tool as the party's intent to have an adverse decision reconsidered, which together with the name 'appeal' makes the action clear: file an appeal against a judgment. It is distinguishable from permission-stage siblings by stating that a further appeal to the High Court 'needs permission,' though it never names seek_leave_to_appeal or proceed_with_appeal directly.

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 concrete filing windows (72 hours of judgment, with a special rule for default judgments tied to the set-aside window) and distinguishes routes: a Magistrate's decision can be reheard by the Upper Court without permission, a High Court appeal requires permission. It never explicitly routes the agent to an alternative tool when permission is needed, so it stops short of naming alternatives.

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