edit_ephemeral_message_caption

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

Annotations already state readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true. The description adds only a Bot API version tag ('10.2') and says nothing about permissions, whether the bot must be the sender, what happens on repeated edits, or whether the edit is visible to the receiver.

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?

A single front-loaded sentence with no filler; the core action is stated immediately. It is arguably over-terse, but no sentence is wasted.

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 7-parameter mutation on a specialized ephemeral message type with no output schema, the definition is thin: it omits prerequisites, the meaning of the ephemeral message id, and any behavioral detail. The safety annotations cover part of the burden, but the description does not fill the remaining gaps.

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 71%, so most parameters carry their own descriptions (caption length limits, chat_id, parse_mode enum). The description adds nothing beyond the schema, and two parameters — notably ephemeral_message_id and reply_markup — remain undocumented in both places.

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 gives a specific verb and resource: 'Edit the caption of an ephemeral media message'. The 'ephemeral' qualifier implicitly separates it from edit_message_caption and from edit_ephemeral_message_text/media, though no sibling is named 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?

There is no guidance on when to use this tool rather than edit_message_caption (for normal messages) or edit_ephemeral_message_text / edit_ephemeral_message_media. An agent must infer the distinction from the tool name alone.

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