compose_music

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

Contradicts annotations: description says 'save the output audio file' (write operation), but annotations have readOnlyHint=true. Also adds cost warning but does not compensate for the contradiction.

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?

Front-loaded purpose, uses bullet-like Args section and bold cost warning. Some redundancy in 'Must provide either...' phrase but overall efficient.

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?

Covers basic usage and cost implications, but does not explain relationship with sibling 'create_composition_plan', output format, or return value despite output schema existing. Incomplete for a tool with multiple modes.

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?

Adds value beyond schema by explaining mutual exclusivity between prompt and composition_plan, default directory, and cost warning. However, does not explain the complex nested structure of composition_plan or music_length_ms constraint.

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?

Clearly states the verb 'convert' and resource 'prompt to music'/'save output audio file'. Distinguishes from siblings like text_to_speech by specifying music generation.

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 'Only use when explicitly requested by the user' due to cost. Lists required parameter combinations but does not explicitly compare with sibling 'create_composition_plan' or explain when to use prompt vs composition_plan.

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