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

With no annotations, the description carries the full behavioral burden and does so richly: it states the once-only constraint, that the old judgment stays published but is marked cancelled with orders not taking effect, and the credential (party) and cost (free). These are exactly the mutation effects and prerequisites an agent needs.

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 content is information-dense and front-loaded with the core action, and each clause adds a real constraint. The opening framing ('The Court decided against me...') is slightly narrative and first-person, which delays the imperative and is minor wasted space.

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 tool with no annotations and no output schema, the description covers behavior, availability, cost, and source thoroughly. Its one real hole is the unexplained parameters (matterId, text, defence structure), which the empty schema coverage leaves unfilled.

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 0% across 3 parameters, including a nested 'defence' object, so the description must compensate. It only loosely implies the 'defence' content ('submit your missing defence') and says nothing about matterId or text, leaving two 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 states a specific action (submit the missing defence to cancel a default judgment) tied to a specific situation and resource. It also names the alternative route (an appeal) once the window closes, so an agent can distinguish it from the many appeal-related siblings without opening a schema.

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 explicit conditions: use within 72 hours of the default judgment, available only once, and after the window closes the route is an appeal. This is a clear when-to-use and when-not-to-use with a named alternative.

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