delete_group_message

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

With no annotations, the description fully carries the burden: discloses that deletion sends a request to group members, works on Signal 5.0+, may fail on older clients, and does not remove the message from local store. Also notes only own messages can be deleted.

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?

Concise, front-loaded with purpose, then provides usage guidelines, alternatives, caveats, and limitations. Every sentence serves a purpose with no 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?

Given 2 parameters, no output schema, and no annotations, the description covers all necessary behavioral context: purpose, constraints, source of timestamp, failure modes, and local vs remote effects. It also distinguishes relevant siblings.

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 covers both parameters with descriptions, but the description adds value by explaining that target_timestamp is the sent_at timestamp from get_conversation, which aids correct parameter usage.

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?

States specific verb and resource ('Remote-delete a message you previously sent to a Signal group') and distinguishes from sibling tools by explicitly naming admin_delete_message for admin deletion and delete_message for direct messages.

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 ('when you want to retract a message you sent in a group') and when not to use ('Do NOT use for direct messages — use delete_message instead'), plus provides source for target_timestamp.

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