Remove locally stored messages for a specific contact or group without affecting the sender's copy on Signal.
Delete locally stored messages for one contact or group. Does NOT unsend from Signal — only removes from local store.
| Name | Required | Description | Default |
|---|---|---|---|
| recipient | Yes | Phone number or group ID whose messages to delete |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description carries full burden. It discloses key behavioral trait: only local deletion, no unsend. This is sufficient for a simple operation, though it omits any mention of reversibility or permission requirements.
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 action, no wasted words. Every part adds value: what it does, scope, and what it does not do.
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 simple tool with one parameter and no output schema, description fully covers purpose, scope, and limitation. No gaps given complexity.
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 100% for the single parameter 'recipient', which is described as 'Phone number or group ID whose messages to delete'. The tool description does not add meaning beyond the schema, meeting baseline.
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 clearly states 'Delete locally stored messages for one contact or group', specifying the verb (delete) and resource (locally stored messages). It distinguishes from siblings like delete_message by noting it does not unsend.
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 'Does NOT unsend from Signal — only removes from local store', informing when to use (local deletion) and when not to (if unsend needed). Does not name specific alternative tools but context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.