Search lyrics by word

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

Beyond the readOnly/idempotent annotations, the description reveals that lyrics.com returns loose and title-only matches, so results are locally filtered to keep only genuine matches. It also explains pagination behavior ('One call returns one page... increase page rather than limit') and the impact of verify='none' to see the raw unfiltered list, offering rich behavioral context.

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 five sentences, each serving a purpose: purpose, return content, usage scenario, pagination semantics, and filtering behavior. It is front-loaded with the core action and contains no extraneous words or redundancy.

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 has 5 parameters and an output schema, the description still provides a complete overview: what is returned, when to use it, how pagination works, how filtering works, and how verification options affect results. It leaves no major questions about invocation or expectations.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by clarifying the functional difference between 'page' and 'limit' and by explicitly describing the effect of verify='none', which is not fully captured by the schema's parameter descriptions alone.

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 opens with 'Search lyrics.com for songs whose lyrics contain a given word or phrase,' which is a specific verb, resource, and scope. It clearly differentiates from siblings by mentioning that the returned id and URL are needed to fetch full text with get_lyrics, positioning search_lyrics as the lookup-by-lyric tool.

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 explicitly states when to use it: 'Use this when someone remembers a fragment of lyrics but not the song, or wants songs mentioning a word or theme.' It also provides page/limit usage guidance, but does not explicitly name search_songs as the alternative for title-based searches, which would have made it a 5.

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