Generate music

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

No annotations are provided, so the description carries the full behavioral burden. Beyond naming the default bot (Lyria) it says nothing about authentication, cost/rate limits, latency, whether generation is synchronous, or what happens when model/parameters are omitted or a flag is ignored. The 'Use when a bot ignores parameters' note lives in the schema, not here.

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?

Two sentences, front-loaded with the action and bot default, and the parenthetical model list is compact. The second sentence duplicates the schema's prompt description, which is the only wasted space.

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 six-parameter, nested-object tool with no annotations and no output schema, the description leaves meaningful gaps: it never explains the relationship between duration_seconds, prompt_flags and parameters, does not mention where generated files land (output_dir), and does not indicate what the caller receives back. It is adequate to start a call but not complete.

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 schema already documents all six parameters, establishing a baseline of 3. The description adds one genuinely new fact — the default model is Lyria and which alternatives exist — but its prompt guidance simply restates the schema's 'Genre, mood, tempo, instruments' wording and adds no format or interaction details for parameters/prompt_flags/duration_seconds.

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 and resource ('Compose music or sound from a text prompt') and names the bot family it targets (Poe music bots, default Lyria), which separates it from generate_image, generate_video and generate_speech. It does not, however, clarify how it differs from the generic sibling generate_with_poe_bot, which sounds like it could also reach a music bot.

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?

Usage is implied rather than stated: the reader infers this is the tool to pick when music or sound is wanted. There is no explicit when-not guidance, no prerequisite (Poe auth/credits), and no routing rule versus generate_with_poe_bot or list_poe_models, so selection still requires inference.

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