Delete all messages by a user in a chat

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

Annotations already declare destructiveHint=true and openWorldHint=true, aligning with 'Wipe every message'. The description adds scope (channel/supergroup) but does not mention irreversibility, permission needs, or the effect on the user's access, which would provide additional transparency beyond 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 a single clear sentence with no filler words. It front-loads the primary action and scope, making it easy to parse quickly.

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 tool with a simple destructive operation and no output schema, the description captures the essential context: what gets deleted and in which context. However, it omits parameter semantics for accountId and any behavioral caveats, which keeps it slightly shy of a full 5.

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 must compensate for parameter semantics. It hints that 'user' names the message author and 'peer' identifies the channel/supergroup, but it does not clarify the meaning or format of 'accountId', nor does it explain the relationship between the parameters beyond implicit mapping.

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 ('Wipe') and resource ('every message a given user has posted in the channel/supergroup'), clearly distinguishing this from sibling tools like delete_messages or delete_saved_history. It conveys both the action and scope effectively.

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 implies the use case (removing all messages by one user in a group), but it does not explicitly state when to prefer this tool over alternatives such as delete_messages or restrict_user. No exclusions or prerequisites are given.

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