create_composition_plan

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

Description states it creates a plan, implying mutation, while annotation readOnlyHint=true suggests a read operation. Therefore, it contradicts annotations and fails to disclose behavioral traits accurately.

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 with purpose, followed by parameter list. Some extraneous information (rate limiting) but overall efficient. Could be slightly more concise.

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 all parameters, cost implications, and relationship to compose_music. Output schema exists so return values are not needed. Does not explain the complex nested structure of source_composition_plan, but schema covers that.

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 meaningful descriptions for all three parameters beyond the bare schema: prompt semantics, music_length_ms range and optionality, source_composition_plan purpose. Schema coverage is 0%, so description compensates fully.

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 it creates a composition plan for music generation, with specific verb and resource. Distinguishes from sibling compose_music by mentioning that plans are used with it.

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?

Provides context on cost (no credits) and rate limiting, and explicitly links to compose_music tool. Lacks explicit when-not-to-use guidance but implies usage for plan generation.

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