Upload a release animated cover video

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

No annotations exist; the description fully carries the burden. It discloses that the video is uploaded to storage and processed asynchronously, suggests checking state via get_release_file, and warns about immutability after distribution.

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 sentences with no waste: first states purpose, second explains processing workflow, third adds immutability and alternative tool. Front-loaded and efficient.

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 tool with 3 required parameters and no output schema, the description covers purpose, behavioral details, and related tools. It mentions a follow-up action (check state) and immutability, making it actionable, though return format is not described.

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 100%, so the schema already documents all parameters. The description adds minimal extra context (e.g., 'finalized animated cover') but does not significantly enhance understanding beyond what the schema provides.

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 clearly states the verb 'Upload' and the resource 'animated cover video for a release', specifies the two variants (square and tall), and distinguishes it from the sibling tool upload_release_artwork for static cover art.

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 advises uploading before distribution because the asset becomes immutable once live, and explicitly recommends upload_release_artwork for static images. It lacks explicit guidance on when not to use this tool beyond that.

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