edit_ephemeral_message_media

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

The annotations already declare a non-read-only, idempotent, non-destructive, open-world mutation, so the safety profile is covered. The description adds only a Bot API version tag and says nothing about what media requires (file_id, URL, or attachment), whether editing clears or preserves other message parts, or whether the token and permission constraints for ephemeral messages apply. For a mutation tool with this many unknowns, that is thin.

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 single sentence is front-loaded and free of filler, but it is too sparse rather than appropriately concise. The parenthetical API version adds little for the caller, while the details an agent actually needs are missing. Structure is clean, but regulation of length is poor.

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 five-parameter mutation with no output schema, an untyped media parameter, and partial required fields, the description should explain acceptable media forms, the receiver semantics, and the outcome. It does none of these, so it is far from complete. Annotations cover safety, but not the operational questions the agent will face.

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 only 40%, and the description compensates for none of it. The two central parameters, media and reply_markup, are declared as empty objects ({}), so they have no type, shape, or description anywhere. ephemeral_message_id is undocumented as well, so the agent has to guess the format for the very field that identifies the target message.

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?

States a specific verb (Edit) and a specific resource (media of an ephemeral message), so the agent can distinguish it from the sibling tools edit_ephemeral_message_text, edit_ephemeral_message_caption, and edit_ephemeral_message_reply_markup. However, it never names those siblings explicitly, so the differentiation is only implied by the resource noun.

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, when not to use it, or which sibling to use instead when the change is to the text, caption, or reply markup rather than the media. It also gives no prerequisites, such as the requirement that the user be the receiver of the ephemeral message, so the caller must infer all of this context.

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