Delete message

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

The description richly discloses the tool's behavior beyond the destructiveHint annotation: the first call deletes nothing and returns a preview plus confirm_token, and deletion only happens on repeated call with the token. It also mentions dry_run support, adding significant operational context.

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 concise at three sentences, with each sentence serving a purpose: stating what it does, explaining the confirmation flow, and giving usage guidance. It is front-loaded with the core action and avoids unnecessary words.

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 and two-step confirmation mechanism, the description covers the essential operational details: how to call it safely, what to expect (preview and token), and when to use it. It is sufficient for an agent to correctly select and invoke the tool, especially with the supportive schema and 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?

The schema already describes 5 of 6 parameters (83% coverage), but the description adds important context for dry_run and confirm_token, which are central to the two-step flow. It compensates for the undocumented dry_run parameter and clarifies how confirm_token is obtained and used.

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?

Purpose is stated clearly and specifically as 'Delete one message,' distinguishing it from bulk_delete_messages and other delete tools. The two-step confirmation flow is also described, which sets it apart from direct-deletion tools.

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 explicitly says to use the two-step flow to let the user approve through the conversation, providing a clear context. It also states the tool is safe to call directly, implying when to invoke it. However, it does not explicitly name alternative tools like bulk_delete_messages for multi-message deletion, so it misses a direct comparison.

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