update_message

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

With no annotations, the description covers core behavior (replaces content, bot-only constraint, returns JSON confirmation). However, it lacks details on error handling, permissions, or idempotency, leaving some behavioral gaps.

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?

The description is succinct with a clear intro, a usage note, parameter list, and return value. No unnecessary words.

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 simple update tool with two parameters and an output schema, the description covers the main purpose, parameters, and return. It lacks information on error conditions or prerequisites, but is largely adequate.

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%, but the description provides brief descriptions for both parameters ('Message ID to update' and 'New content (plaintext)'), adding meaning beyond schema titles and types. It does not specify constraints like length limits.

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 clearly states 'Update a bot message' and 'Replaces the content of an existing bot message.' It distinguishes from user messages by referencing 'user_send_message' tool for user messages.

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 description explicitly states that only bot-sent messages can be updated and suggests using 'user_send_message' for user messages, providing clear guidance on when to use and when not to use this tool.

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