Download Beat Edit

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is largely covered. The description adds only the 'finished' precondition and says nothing about why a download would be flagged destructive, whether it overwrites an existing file at outputPath, or auth/rate constraints.

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?

A single tight sentence with the artifact and format front-loaded; no wasted words. It is efficient, though brevity here partly reflects under-specification rather than discipline.

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 two required params, no output schema, and no explanation of the download destination behavior, an agent lacks enough to invoke confidently: the meaning of 'id', overwrite behavior, and error handling are all unaddressed for this open-world download tool.

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 50%: outputPath is documented in the schema, but the required 'id' parameter has no description anywhere. The phrase 'to a local .mp4' loosely reinforces outputPath, yet the description does nothing to clarify what 'id' identifies or its format.

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 (Download), a named resource (Beat Edit), and the output artifact (.mp4), which clearly distinguishes it from siblings like download_clip and download_all_clips. It does not, however, explicitly name those siblings or contrast its scope against them.

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 word 'finished' hints at a prerequisite (the edit must be complete, likely per beat_edit_status), but there is no explicit when-to-use, no mention of the beat_edit/beat_edit_status workflow, and no guidance on how to choose this over download_clip or download_all_clips.

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