purge_messages

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

No annotations are provided, so the description must disclose behavioral traits. It states the 14-day restriction but does not explicitly emphasize that deletions are permanent or that the operation is destructive, which is important for a delete tool. It also doesn't mention permission requirements. This is a partial gap.

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, concise sentence that front-loads the core purpose. No filler or redundancy.

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?

While an output schema exists (which covers return values), the description lacks clarity on edge cases such as what happens if count exceeds 100 or if messages are older than 14 days (fail vs. skip). It also omits permission prerequisites, but the core function is conveyed. Given the simplicity of the operation, it is mostly adequate but not fully comprehensive.

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. It implies count is the number of messages and channel_id identifies the channel, but it does not explain the 'reason' parameter at all. It adds some context but leaves one parameter underspecified.

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 action (bulk delete), the resource (messages), and the scope (up to 100 recent messages in a channel). It distinguishes from sibling tools like delete_channel by focusing on message-level deletion.

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 specifies when to use (bulk delete recent messages) and includes a key limitation (messages older than 14 days cannot be bulk deleted), which helps the agent decide applicability. However, it does not explicitly mention alternatives or exclusions, though no direct sibling serves the same purpose.

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