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

Beyond the annotations, it discloses two behaviors that matter: the automated assessment is re-run and updated as a side effect, and this is rate-limited ('a limited number of times per case'). It also flags credential sourcing (case_id/case_token from submit_escalation). It doesn't say what happens when the limit is hit or whether addenda accumulate, so not 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?

Two sentences, front-loaded with the action and followed by the side-effect and prerequisites. The mid-sentence enumeration is slightly long but each item clarifies what can be added.

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 4-parameter mutation tool with no output schema, the description covers the action, the side effect, the rate limit, and where the required credentials come from, and routes the agent to check_escalation for output. It does not contradict the non-readOnly, non-idempotent, non-destructive annotations.

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 coverage is 100%, so every parameter including the nonce is already documented. The description only reinforces the credential provenance (from submit_escalation) and hints at the message content, which is a baseline-level addition rather than new detail.

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?

Specific verb+resource ('Add information to an escalation case') with a concrete enumeration of what counts as information (decisions, principal replies, contact details, team requests). It clearly distinguishes itself from submit_escalation (creates the case) and check_escalation (reads the assessment).

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?

Gives clear context for when to use it — after a case exists — and points to check_escalation for reading results and submit_escalation as the source of the required credentials. It omits an explicit 'do not use when' condition, but the case-scoped framing is sufficient for correct routing.

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