recall_message

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

The description adds significant behavioral context beyond the annotations. It details the permanent deletion for all members, time limits, permission requirements, and the source of message_id. This fully informs the agent of the tool's side effects and constraints, complementing the destructiveHint=true annotation.

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 well-structured with a clear first line, parameter details, usage conditions, and a final note. While it is slightly verbose, every sentence adds necessary information. Front-loading of the core purpose is good, though the parameter explanation could be integrated more concisely. Overall, it is effective without excess.

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 has one simple parameter, no output schema, and annotations already cover destructiveness, the description is fully complete. It covers permissions, time constraints, message source, scope (only bot's messages), and the permanent deletion effect. No important aspect is missing for correct usage.

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 has one parameter (message_id) with no description in the schema itself. The tool description fully explains what message_id is, where to obtain it (from send_message or send_image responses), and its role in the operation. This adds complete semantic meaning beyond the schema's type and required status.

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 that the tool recalls (deletes) a message sent by the bot. It specifies the action ('Recall (delete)'), the target resource ('a message sent by the bot'), and distinguishes it from sibling tools like send_message or send_image by focusing on deletion. The purpose is unambiguous and specific.

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 guidelines on when to use the tool ('Use this to undo accidental sends') and constraints (only within 2 minutes unless bot has admin/owner privileges, cannot recall other users' messages). It implicitly tells the agent not to use it for messages from other users. While it does not explicitly name alternative tools, the context is sufficient for correct selection.

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