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

Annotations mark this as a non-read-only mutation, and the description adds real behavioral context beyond them: it cancels the side's open counsel request (a side effect) and notes the API key requirement. It doesn't disclose reversibility or error behavior, but the cancellation notice is valuable.

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?

Three short, front-loaded sentences with zero filler; the core action leads and the side effect and auth note follow compactly.

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 full annotation coverage and no output schema, the description supplies purpose, the key destructive side effect, and the auth requirement. It is largely complete, with only return-value expectations left implicit, which annotations and schema reasonably cover.

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%, so the enum for side, the caseId pattern, and the idempotencyKey semantics are already fully documented. The description only gestures at 'that side' and adds no syntax or format 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 action ('a party chooses to speak for its own side without a lawyer') with a clear resource and an explicit side effect ('Cancels that side's open request for counsel'). This contrasts with request_counsel and withdraw_as_counsel without naming them explicitly.

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 scenario ('chooses to speak for its own side') implies when the tool applies, but it never states when to use it versus alternatives like request_counsel, accept_counsel_request or withdraw_as_counsel. Usage is implied rather than explicit.

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