delete_message

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

Beyond the destructiveHint annotation, the description reveals that revoke=True makes deletion irreversible and triggers an 'elicit' confirmation plus a PreToolUse hook. This is significant behavioral information that helps the agent understand side effects and safety protocols, exceeding what annotations alone provide.

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 extremely concise, with the main purpose in the first sentence and a focused parameter breakdown in the next. Every word adds value, and the structure front-loads the essential information.

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?

Given the tool's destructive nature, the description effectively covers the core decision (revoke or not) and its consequences. The presence of an output schema reduces the need to describe return values. However, it omits details about parameter formats and potential error conditions, leaving minor gaps for a destructive operation.

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?

The input schema has 0% description coverage, so the description must compensate. It explains the most important parameter, revoke, including its default and irreversibility. However, chat and message_ids are not elaborated—chat accepts integer or string, but the difference is not clarified. Thus, compensation is partial.

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 clearly states the primary function: 'Удалить сообщения' (delete messages) and immediately clarifies the default scope 'только у себя' (only for yourself). This distinguishes it from other deletion tools like delete_dialog or delete_stories, making the purpose unambiguous.

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 provides clear context for each mode: default is delete only for yourself, while revoke=True deletes for everyone and triggers a confirmation flow. It effectively tells the agent when to set the revoke flag, though it does not explicitly name alternative tools or exclusion conditions.

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