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

Annotations declare non-read-only, non-idempotent, non-destructive, open-world. The description adds what carries over (lyrics unless replaced), what the output is (two songs for same Gold), and that a jobid routes to mureka_get_job. It doesn't state rate limits or what happens to the original song, but adds substantial behavioral context beyond annotations.

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?

Four sentences, each earning its place: core action, carryover/scope, alternative routing, and output/job routing. Front-loaded with the main purpose.

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 6-param creation tool with full schema coverage and annotations, this is nearly complete: it explains output shape and routing. Missing only edge cases like what happens to existing song or failure modes, but nothing critical for correct invocation.

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 100%, so parameters are fully documented. The description adds some implications (lyrics apply only with vocals, desc default is original style), but baseline 3 applies when schema already does the heavy lifting.

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 ('Re-record a whole song') with clear scope (whole song, vocals or instrumental) and names the sibling mureka_edit_section for partial changes. An agent can distinguish it from all other mureka_* creation tools.

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?

Explicitly says to use mureka_edit_section when changing only one part, and clarifies that for instrumental-only desc, title and model apply. This is clear when/when-not guidance with a named alternative.

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