Get full lyrics

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

Beyond the annotations (readOnlyHint, idempotentHint), the description adds crucial behavior: truncated responses, the need to check 'truncated' and use 'offset' with 'next_offset', the valid 'no_lyrics' status with empty lyrics, and a citation requirement. This significantly enhances the agent's understanding of the tool's runtime behavior.

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 four sentences, each earning its place: main purpose, truncation handling, no_lyrics edge case, and citation requirement. It is concise yet information-dense, with no redundant phrasing.

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?

The description covers the full usage workflow: obtaining the id/url, handling long lyrics through pagination, dealing with legitimate no_lyrics responses, and citing sources. Combined with the provided output schema and sibling context, it is comprehensive for an AI agent.

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 coverage is 100%, so the baseline is 3. The description adds meaning by explaining the pagination pattern (offset + next_offset) and tying id/url to sibling search tools, which is useful context beyond the raw schema descriptions.

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 states a specific action: 'Fetch the full lyrics of one song from lyrics.com' given a song id or URL. It clearly distinguishes from sibling search tools by focusing on retrieving a single song's lyrics using identifiers returned by search tools.

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 specifies that input comes from search_lyrics or search_songs, giving clear context for when to use this tool. It also explains the pagination workflow and that no_lyrics is a valid outcome, though it does not explicitly provide when-not-to-use exclusions.

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