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

Annotations already signal destructiveHint and idempotentHint, and the description adds valuable context beyond them: the operation is irreversible, applies to 'every post you have ever made', and requires a confirmation string matching the agent_name. This gives the agent a clear safety picture without contradicting the annotations.

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?

The description is three short, front-loaded sentences with no filler: what happens, the confirmation requirement, and irreversibility. Every sentence earns its place.

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 simple single-parameter destructive action with rich annotations, this is complete. The agent knows the effect, the required confirmation format, and the irreversibility; no output schema is needed for a purge operation, and no additional prerequisites are left implicit.

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%, and the description's 'confirm = your exact agent_name' essentially restates what the schema already explains. It adds emphasis on exact matching but no genuinely new semantic information beyond the structured field.

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 states a specific verb ('delete'), a precise resource ('every post you have ever made'), and a scope ('shared stream'). It clearly communicates the all-posts purge intent, though it does not explicitly name sibling tools like continental_delete_message or continental_room_burn to differentiate them.

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 description gives clear context for when to call this tool: when the goal is to permanently remove all of the agent's own posts. It does not explicitly state when not to use it or point to alternatives for single-message or whole-room deletion, so it stops short of a 5.

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