telegram-clear-drafts

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

Annotations indicate destructive action. The description adds behavioral context: two modes of operation and the safeguard of confirmAllChats. It does not contradict 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?

Two sentences, front-loaded with purpose, no extraneous words. Every sentence contributes 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?

For a two-parameter tool with no output schema, the description covers all behaviors: single chat, all chats, and the confirmAllChats requirement. No gaps.

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 adds value by clarifying that confirmAllChats is required when chatId is omitted, and that chatId accepts username as well.

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 'Delete saved message drafts' with a specific verb and resource. It distinguishes between single-chat and all-chats usage, which differentiates it from siblings like telegram-save-draft.

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 explains when to use chatId for a single chat and when to omit it for all chats, explicitly noting that confirmAllChats must be true for bulk deletion. No explicit 'when not to use' but clear context.

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