producer_get_lyric_format_guide

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

No annotations are provided, but the description clearly indicates this is a read-only retrieval of a guide. It discloses that the tool returns 'complete guide with section markers, examples, and tips,' which is sufficient behavioral context. It does not contradict any annotations (none present).

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 concise at six lines, with a clear front-loaded sentence. However, there is minor redundancy between 'Get guidance' and 'Shows how'; it could be slightly tighter without losing meaning.

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 simple retrieval tool with no parameters and an existing output schema, the description adequately covers what the tool does and returns. It could add a note about when to call this in a workflow (e.g., before generating music), but the current text is sufficient for the agent to understand the tool's role.

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 input schema has zero parameters, so the baseline is 4. The description adds value by explaining what the guide contains (section markers, examples, tips), which helps the agent understand the output without needing parameter details.

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's purpose: 'Get guidance on formatting lyrics for Producer music generation.' It specifies the resource (guidance), the verb (get), and the domain (formatting lyrics). The tool is distinct from sibling generation tools like producer_generate_lyrics, as it provides a reference rather than creating content.

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 implies usage context by stating that following the format helps Producer understand song structure, but it does not explicitly state when to use this tool versus alternatives (e.g., before generating lyrics or music). No mention of when not to use it or prerequisites, which leaves some ambiguity for an AI agent.

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