delete_message

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

No annotations provided, so description carries full burden. Discloses that deletion sends request to recipient, requires Signal 5.0+, only works for own sent messages, may fail silently, and does not remove from local store (pointing to delete_local_messages).

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?

Single paragraph with multiple sentences, each serving a purpose. Slightly long but well-organized. Could be broken into bullet points for readability, but overall efficient.

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 deletion tool with no output schema, description covers behavior, constraints, parameter details, and alternatives. Missing return value information, but not critical for this type of tool.

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%, but description adds context: target_timestamp is described as 'sent_at timestamp from get_conversation', and recipient is clarified as phone number. Provides meaning beyond raw schema.

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?

Description states specific action: remote-delete (unsend) a message you sent to a Signal contact. Clearly distinguishes from sibling tools by naming alternatives like delete_local_messages, delete_group_message, and admin_delete_message.

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?

Explicitly states when to use ('retract a sent message from recipient's device') and when not to ('Do NOT use for group messages, use delete_group_message instead; Do NOT use to delete a message you received'). Also notes silent failure on older clients.

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