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

Annotations only say readOnlyHint=false; the description goes much further by stating who loses access, that the action is shared across participants, and that a minimal retry tombstone remains. These behaviors are not derivable from the structured data and are exactly what an agent needs to predict side effects.

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 sentences, each carrying distinct information: the operation, the access consequence for the other participant, and the retry tombstone behavior. There is no filler or repetition of schema fields.

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 one-parameter destructive tool with an output schema, this description covers the essential operation, participants, access revocation, and retry semantics. It could add explicit irreversibility or error-condition context, but nothing critical is missing for selecting and invoking the tool.

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?

With 0% schema description coverage, the description should compensate by explaining task_id, but it never references the parameter or how it identifies the terminal task. The schema pattern and required flag provide format constraints, but the description itself adds no parameter-level meaning.

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?

The description uses a specific verb ('erases') and a clear resource ('shared content of a terminal task'), and it conveys the consequence that both participants lose access. It does not explicitly differentiate itself from siblings like cancel_task, but the shared-content deletion scope is distinct enough to identify the tool's purpose.

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?

It gives clear context about when the tool applies: only a terminal task, and only by either participant. It does not explicitly state when not to use it or name alternatives, but the terminal-task precondition is a meaningful usage boundary.

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