generate_music

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

Annotations are absent, so the description carries the full disclosure burden, yet it only restates the core action. It discloses nothing about non-determinism (despite the seed parameter), cost or credit consumption (estimate_cost exists as a sibling), latency, or how generated audio is returned. There is no contradiction, but almost no behavioral context beyond the tool's purpose.

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?

The definition is a single nine-word sentence with zero filler, front-loading the verb and resource. It is efficient, though the brevity reflects under-specification rather than rich compression of information.

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 an 8-parameter generation tool with no annotations and no output schema, this is thin. The description says nothing about output format, the display/save/both behavior of display_mode, model selection, or cost implications, so an agent must infer critical invocation details from the schema alone. A few sentences covering output behavior and model guidance would be needed for completeness.

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 the baseline of 3 applies even though the description adds no parameter detail. The only marginal contribution is mapping 'text descriptions' to the prompt parameter; semantics for model, duration, display_mode, and save_location are entirely delegated to the schema.

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 and resource — 'generate music' from 'text descriptions' — making the tool's core function unmistakable. It does not, however, distinguish itself from the sibling generate_audio, leaving real ambiguity about whether music or general audio generation is intended.

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?

No when-to-use guidance is provided whatsoever. The description never mentions alternatives, exclusions, or selection conditions, and given the overlapping sibling generate_audio, the boundary between 'music' and 'audio' is left entirely to the agent's inference. This is simply absent guidance.

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