Update Chat Message

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

With no annotations, the description carries the full behavioral burden, and it does disclose one genuinely important trait: this is a mutation gated behind confirm=True. It says nothing about permission prerequisites, whether edits are reversible or leave edit history, or how conflicting concurrent edits are handled.

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 short, front-loaded sentences with zero filler: the operation comes first and the confirm gate second. Nothing could be removed without losing signal, though the brevity costs detail captured in other dimensions.

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 mutation tool with no annotations, no output schema, and an unconstrained nested body object, the definition is too thin. An agent still cannot determine what to put in body or what a successful/denied edit returns, which are exactly the gaps the description should close.

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 0% across four parameters, and the description only clarifies one of them (confirm=True). The required body parameter is a free-form nested object with additionalProperties=true, and the description gives no hint of its expected shape, while chat_id and message_id remain entirely unexplained.

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?

The description uses a concrete verb and resource ("Edit the text of your own message in a chat"), which clearly separates it from siblings like delete_chat_message and send_chat_message. It also scopes the operation to the caller's own messages, though it never names a sibling explicitly.

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?

The phrase "your own message" implies a permission boundary and distinguishes editing an existing message from sending a new one, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative for editing messages that aren't yours.

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