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 fairly well: it discloses the required credential ('party'), that the operation is free, the governing source (Rule 4.10), and a meaningful side effect (the passage receives the highest source grade). It stops short of stating reversibility, idempotency, or what the response looks like.

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?

Two short sentences plus a compact credential/cost/source tag, with the action stated up front. Nothing is wasted, though the first-person 'I agree that...' framing is slightly awkward for a tool description.

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 and no output schema, it covers credential, cost, governing rule, and the key outcome effect, which is more than many peers. It still omits parameter identification, id format, and any notion of reversibility or result, so an agent could invoke it but not with full confidence.

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%, so the description is the only source of parameter meaning. It loosely maps to the two params via 'for this case' (matterId) and 'the other side supplied' passage (tenderId), but never identifies them, gives no id format, and leaves an agent guessing which value goes where.

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: it records the party's acceptance that a legal passage supplied by the opposing side is accurate, and assigns that passage the highest source grade. The effect on the passage is concrete and understandable. It does not, however, name its obvious counterpart dispute_tender, so sibling differentiation relies on inference.

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?

'Staying silent does not count as acceptance' implies an active step is required, which is useful context. But there is no explicit when-to-use guidance, no statement of when to use this versus dispute_tender, and no prerequisites beyond the credential note. Usage is implied rather than instructed.

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