Get lyrics

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing further — no note on availability, licensing/region limits, or what is returned when lyrics are unavailable.

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?

It is a single short fragment with no waste, but that brevity reflects under-specification rather than disciplined conciseness. There is nothing to front-load because nothing meaningful is said.

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?

No output schema exists, so the description carries the burden of conveying return behavior, yet it says only 'Lyrics for a song.' For a lookup tool with no output schema, this leaves the agent without any sense of the response shape or failure modes.

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% and the sole parameter's origin (from get_album tracks or search_songs) is fully documented in the schema. Per the baseline rule, high coverage with a silent description still lands at 3.

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 'Lyrics for a song' essentially restates the tool name and title without adding a specific verb+resource framing beyond what the identifier already conveys. It does not distinguish this tool from siblings like get_album or search_songs beyond the implicit resource name.

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?

There is no guidance on when to call this versus alternatives. The only routing hint lives in the schema param description ('from get_album tracks or search_songs'), not in the tool description itself, so the description provides no usage context.

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