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

Annotations only flag readOnlyHint=false; the description goes much further by disclosing the consequential side effect — that a finished video is saved and payment is taken here, that the result says so, and that links expire after one hour. It also sets polling expectations, which materially changes how an agent should invoke it.

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?

It is dense but every clause carries information, and the return shape is front-loaded. The main flaw is structure: it is one long semicolon-chained paragraph, and the most consequential fact (payment capture) is buried mid-paragraph rather than surfaced early.

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?

With no output schema, the description still conveys the return contents (ids, one-hour private links, in-progress items, clone status) in prose. For a zero-parameter tool with no output schema, nothing an agent needs in order to call and interpret it is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already shows. Baseline 4 for a parameterless tool is appropriate.

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 names a specific resource and scope: the signed-in member's Studio, listing the images and videos they made, plus in-progress work and clone status. This clearly separates it from siblings like studio_make (creates) and my_photos/my_posts (other content types) without needing to open any schema.

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?

It gives two concrete use cases: find an image's id before turning it into a video, and check whether a video has finished. It also advises re-checking in a minute rather than polling repeatedly. Sibling alternatives (e.g. studio_make) are implied rather than named, so it stops short of full when-not guidance.

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