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

ReadOnly annotation is reinforced and expanded: URL is temporary, receipt is durable, and the tool cannot create exports. This tells the agent about side-effect-free retrieval and a capability limit.

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 dense sentences lead with the core purpose, then clarify parameter semantics and limitations. No filler.

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?

Covers the return behavior (temporary URL, durable receipt) and main kind values, but omits edl_version, response shape, and any conditions/errors. Adequate but not complete.

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 0%, so all meaning must come from the description. It explains kind and asset_id well, but says nothing about edl_version and only implies project_id. Partial compensation.

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+resource ('temporary URL for downloading a render') and differentiates itself by clarifying it cannot create a final export, which sets it apart from render/export-style siblings.

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?

Implies when to call it — when you need a download link for a render — and notes a negative boundary (cannot create final export), but gives no explicit guidance on when to prefer this over sibling tools or when not to use it.

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