compose_music

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

The description indicates a write operation (saving an audio file) and an API call incurring costs, but annotations set readOnlyHint=true, creating a direct contradiction that undermines transparency.

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 description is well-structured with a clear main sentence, bullet points for arguments, and a cost warning, though slightly verbose; it earns its sentences without significant redundancy.

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?

The description covers key parameter behaviors and cost implications but omits return value details (despite an output schema) and is hampered by the annotation contradiction, leaving the agent with incomplete context.

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?

With 0% schema coverage, the description effectively explains each parameter, including constraints like mutual exclusivity and default behavior, adding value beyond the raw 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 clearly states the tool converts a prompt to music and saves an audio file, distinguishing it from siblings like text_to_speech or text_to_sound_effects by focusing on music composition.

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 description provides some usage guidance, such as the optionality of output_directory and mutual exclusivity of music_length_ms with composition_plan, but does not explicitly contrast with sibling tools or specify when to use this over alternatives.

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