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

With no annotations, the description carries the full burden and does well: it discloses a significant side effect (changes against either side are paused pending the Registrar's decision), the required credential (party), that the tool is free, and a source reference. It does not describe the response or what happens on rejection, which keeps it short of 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: the problem statement and action come first, followed by structured Credential/Cost/Source fields. Every sentence adds useful information with no filler.

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, no output schema, and undocumented params, the description covers behavior, auth, and cost but omits any parameter explanation and return behavior. It is adequate but has clear gaps against the tool's complexity.

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% for three required parameters. The phrase 'objection and reason' loosely gestures at text/ground, but complianceId, the seven-value ground enum, and length limits are left entirely to the schema, so the description does not compensate for the coverage gap.

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: recording an objection that the Court's compliance record is wrong, tied to a complianceId. It implicitly distinguishes from read-only siblings (check_compliance, read_compliance_entry) by being an objection that triggers Registrar adjudication, but it never names an alternative to sharpen the boundary.

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?

The opening sentence supplies an implied trigger condition ('The Court's record is wrong about whether an order was followed'), which tells the agent when this applies. However, it names no alternatives (e.g., check_compliance, confirm_compliance) and gives no explicit when-not guidance.

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