Revert a media asset

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

Discloses that the current copy is archived first, making the revert undoable, which adds behavioral context beyond the annotations (readOnlyHint=false, destructiveHint=false). This helps agents understand the non-destructive nature and side effects.

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 concise sentences that front-load the core action and key behavior, then provide a useful usage hint. No redundant 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?

Adequately explains the revert process and where to find version ids, but lacks information about the return value (no output schema) and any prerequisites like permissions or state requirements. With 3 parameters and no output schema, more detail would improve completeness.

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?

Only the 'version' parameter is explained in the schema, but the description adds context by mentioning get_media for version ids. However, 'project' and 'name' parameters lack any description or guidance beyond the schema, so the overall coverage is moderate.

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?

Clearly states 'Restore a prior version of an asset as the current one', which is a specific verb+resource action. It distinguishes itself from sibling tools like get_media (read) and edit_media (modify) by focusing on version restoration.

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?

Provides explicit guidance to use get_media to find the version id, helping agents understand the prerequisite. However, it does not specify when not to use this tool or mention alternative tools for other revert scenarios.

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