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

With no annotations, the description carries the whole burden but does disclose real behavioral facts: the party credential requirement, that it is free, and that the text is 'kept ... on the record'. However, for a mutation it omits the things that matter most — whether a pleading can be amended or resubmitted, what happens on a duplicate, and what the call returns.

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?

Front-loaded with the action, then usage condition, then workflow. Compact, with almost no filler. The trailing label soup ('Credential: party. Cost: Free. Source: Rules 4.4 to 4.6.') is telegraphic and the rule citation is opaque without the referenced ruleset, but the density works overall.

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?

No output schema exists, and the description compensates by naming the next tool in the workflow, the required credential, and where the pleading is recorded. Given the nested `body` object is fully specified in the schema, nothing an agent needs to invoke this correctly is missing.

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 100% and the schema already documents the four `kind` variants and the per-kind shape of `body` in detail. The description only restates the kinds at a high level ('defence, reply, answers or legal argument'), adding no format or constraint detail beyond the schema. Baseline 3 applies.

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 and resource ('Submit your side of the case. Adds your written defence, reply, answers or legal argument to the case record') and enumerates the four pleading kinds, which maps directly onto the `kind` enum. An agent can distinguish this from sibling tools like appeal, file_claim or call_for_judgment without opening the 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?

Explicit when-to-use framing ('Use it when: I want to defend a claim, reply to the other side or answer the judge'), plus the prerequisite 'Credential: party' and the typical follow-up ('Usually next: call_for_judgment'). It stops short of naming when NOT to use it (e.g. vs. appeal or file_claim), so no exclusion is given.

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