edit_message

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

Discloses editing behavior: sends via signal-cli, recipients see '(edited)' label, only text modifiable, must reference exact timestamp, only own messages, no time limit but Signal may ignore old edits. With no annotations, description fully covers behavioral traits.

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?

Description is concise and front-loaded: first sentence states core purpose. Subsequent sentences add necessary constraints without redundancy. Every sentence adds value.

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?

No output schema, but description covers usage context, constraints, and behavioral details like Signal ignoring old edits. Missing explicit return value info, but overall complete for a mutation 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 baseline is 3. Description adds value by explaining target_timestamp must be exact, recipient vs group_id usage, and that exactly one is required. This clarifies parameter semantics beyond 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?

Clearly states the tool edits the text of a previously sent message. Distinguishes from send_message, delete_message, and other siblings by specifying that only text is modifiable, not attachments or other elements.

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 says when to use: 'Use when correcting a typo or updating information.' Also states when not to use: 'Do NOT use to change who a message was sent to — send a new message instead.' Provides context on editing only own messages and requiring exact timestamp.

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