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

With no annotations, the description carries full behavioral burden. It does add real context: credential requirement (party), cost (Free), and rule source (Rule 4.10). It does not disclose what happens after the challenge is recorded, whether it is reversible, or any downstream consequences, which is a notable gap for a mutation tool.

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?

Four short sentences, front-loaded with the situation and the action. There is mild redundancy between the first sentence's defects ('invented, altered or misleading') and the second sentence's ground list, but overall it is tight and readable.

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 6-parameter mutation with a nested object, no output schema and no annotations, the description covers credential, cost, rule source and the grounds enum. It omits the purpose of text/attested/provenance and any post-submission behavior, so an agent calling it is still partly guessing.

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 6 parameters, including a nested provenance object, so the description must compensate. It partially does by enumerating the four grounds that correspond exactly to the ground enum ('does not exist', 'passage not in source', 'altered', 'context omitted'). It says nothing about text, attested, matterId, tenderId, or provenance, so half the surface remains 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?

States a concrete action ('Records your challenge and reason') against a specific object (the other side's legal quotation), and enumerates the four challengeable defects. An agent can tell this is a challenge-filing tool, though it never names a sibling tool it should be preferred over (e.g. accept_quote, notify_dispute).

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 first-person framing ('I think the other side's legal quotation is invented, altered or misleading') implies the triggering situation, which is genuinely useful. However, there is no explicit when/when-not guidance and no routing against the large family of sibling dispute/accept tools, leaving the choice to inference.

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