Revert a media asset

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

Description notes that the current copy is archived first and the revert is undoable, adding behavioral context beyond the annotations (destructiveHint=false). This helps the agent understand safety. No missing contradictions.

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?

Three concise sentences: purpose, behavioral note, and prerequisite. No fluff, information is front-loaded and structured for quick comprehension.

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?

Lacks return value specification (no output schema) and error handling details. For a simple 3-param mutation tool, the description is adequate but could be more complete about expected outcomes.

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 33% (only version has a description). The description enhances version parameter by linking it to get_media. However, name and project lack added meaning, leaving a gap for those parameters.

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?

Title and description clearly state the purpose: reverting a media asset to a prior version. Uses specific verb 'revert' and resource 'media asset', distinguishing it from siblings like edit_media or save_media.

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?

Description explicitly advises using get_media to find the version id, providing clear prerequisite context. While no exclusions or alternatives are mentioned, the guidance is sufficient for correct invocation.

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