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

Annotations already flag a non-read-only, non-idempotent, open-world write. The description adds real value with 'A job.', signalling an asynchronous submission the agent must poll via flowmusic_get_job. However it never says whether the source clip is modified in place or a new result clip is produced, nor mentions cost or auth scope.

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 short, front-loaded with the core action, and free of filler. The trailing fragments 'A job.' and 'POST /music/edit operation replace.' are telegraphic and only the first carries real meaning for an agent.

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 7-parameter mutation tool with no output schema and no annotations describing outcomes, the description omits the job lifecycle (polling, result retrieval), whether the original clip survives, and any permission or cost context. An agent can attempt the call but cannot predict its consequences.

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 every parameter (including seed, model, title, and the mask bounds) is already documented in the schema. The description only restates mask_start_s/mask_end_s and instruction, adding no syntax or constraint detail beyond the schema, so baseline 3 applies.

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 states a specific verb (regenerate/replace) on a specific resource (one section of a clip bounded by mask_start_s/mask_end_s) and ties the edit to the instruction parameter. It is distinguishable from siblings such as extend_song, cover_song, and apply_effect, though it never names an alternative explicitly.

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?

There is no guidance on when to choose this over flowmusic_extend_song, flowmusic_cover_song, or flowmusic_apply_effect, and no stated prerequisites (e.g., clip must come from a finished job). Usage is only inferable from the word 'section'.

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