edit_message_text

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the action without revealing constraints (e.g., only messages sent by the bot can be edited, permissions required, or whether the edit is reversible). This is a significant gap for a mutating tool.

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 a single, front-loaded sentence with no wasted words. While it is arguably too terse for a tool with three parameters, it achieves conciseness without being verbose.

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 three parameters, no annotations, no output schema, and zero schema descriptions, the description is incomplete. It misses key context such as the constraint that only bot-sent messages can be edited, and it provides no information about return values or failure modes.

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?

The schema provides no parameter descriptions (0% coverage), and the description 'Edit the text of a message' adds no meaning beyond what parameter names imply. It does not explain chat_id, message_id, or text formats, limits, or special values.

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 'Edit the text of a message' uses a specific verb ('edit') and resource ('text of a message'), clearly distinguishing it from sibling tools like send_message (creates) or delete_message (removes). It is concise and unambiguous.

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 gives no guidance on when to use this tool versus alternatives such as send_message or delete_message. It also does not mention prerequisites like the message needing to be sent by the bot or conditions like message age limits.

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