edit_message

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

Annotations already indicate write operation, but description adds no behavioral details beyond parameter names. No mention of effects on other participants or conditions like edit window.

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 one-line summary with parameter definitions. Front-loaded and no extraneous text.

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?

Sufficient for a simple edit tool but lacks details on error responses, access permissions, or time restrictions. Output schema presence mitigates some gaps but description incomplete.

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?

Minimal clarification beyond schema (e.g., 'GUID of message' and 'new text'). No format examples, length limits, or behavior consequences given 0% schema description 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?

Clear verb 'Edit' and specific resource 'previously sent message'. Distinct from siblings like send_message or unsend_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?

No guidance on when to use this vs alternatives (e.g., unsend and resend). No mention of constraints like time limits or sender requirements.

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