producer_generate_lyrics

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

No annotations are provided, so the description carries full burden. It discloses output includes section markers and return fields (title, status, formatted text), but does not mention quotas, rate limits, or any non-obvious behaviors.

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 front-loaded with the main purpose and uses bullet points for usage scenarios. It is concise without fluff, though the 'Returns' line could be slightly more compact.

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?

Given the tool's simplicity (one parameter, clear output schema), the description covers purpose, usage, and output format adequately. It is complete for an agent to decide when and how to use it.

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?

The single parameter 'prompt' has a detailed schema description. The tool description adds value by advising to include theme, mood, genre, and giving examples. Schema coverage is 100%, so baseline 3, with extra context raising it to 4.

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 'Generate song lyrics from a text prompt' and specifies structured lyrics with proper song sections. It differentiates from sibling tools like producer_generate_music and producer_generate_custom_music.

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 includes 'Use this when:' bullet points listing appropriate scenarios. It mentions output is ready for producer_generate_custom_music, but lacks explicit exclusions or comparisons with alternatives like producer_get_lyric_format_guide.

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