edit_message

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

Describes returned confirmation/error and the constraint of editing only own messages. Annotations only have openWorldHint, but description doesn't elaborate on side effects. Minor gap: no mention of behavior if message not found or permission denied.

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 with purpose. Includes usage, return, related tools, and attention note. Could be slightly more structured but effective.

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?

Covers purpose, usage, constraint, and related tools. Output schema exists, so return details are not needed. However, lacks error handling or edge cases.

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 0%, and description does not explain parameter meanings beyond their names. Missing details like text format, length limits, or constraints.

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 the tool edits a sent message by message_id. It uses specific verb and resource, and distinguishes from siblings like delete_message and get_dialog.

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 (fix typos, update text), provides alternatives (delete_message), and highlights constraint (only own messages).

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