Edit WhatsApp Message

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

Adds behavioral info: 'WhatsApp shows an "edited" label on the message after editing.' Annotations already declare idempotentHint=true and nondestructive, but description enriches with user-visible effect.

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?

Four sentences, front-loaded with purpose, each sentence adds value. Could be slightly tighter but still 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?

Includes return info ('confirmation with edited message ID'), sufficient given no output schema. Coverage is adequate for a simple edit 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%, so description repeats parameter info without adding extra meaning. Meets baseline for high coverage.

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 starts with 'Edit a previously sent text message,' clearly stating verb (edit) and resource (message). Distinguishes from siblings like send, delete, forward.

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?

States 'Only works on messages you sent (fromMe=true),' providing a clear condition. No explicit alternatives or when-not usage, 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.