get_lyrics

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

No annotations are provided. The description discloses an authentication requirement (SPOTIFY_SP_DC), adding behavioral context beyond the schema. However, it does not mention rate limits, side effects, or output behavior, leaving gaps that annotations would normally fill.

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 a single sentence, which is concise, but it is under-specified. The brevity comes at the cost of missing essential parameter documentation, making it less useful overall.

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 tool has one simple parameter and an output schema, but the description fails to explain the input or output. Given the low schema coverage (0%) and lack of annotation support, the description is incomplete for reliable tool selection and invocation.

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 one required parameter 'value' with 0% description coverage. The description provides no explanation of what 'value' represents (track ID, URL, etc.), leaving the agent without critical information to invoke the tool correctly.

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 action ('Fetch a track's lyrics') and the specific resource. It is distinct from sibling tools like get_track or get_album, and the verb+resource combination is precise.

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 mentions a prerequisite ('needs SPOTIFY_SP_DC'), which hints at when the tool is usable, but it does not elaborate on when to choose this tool over alternatives like search or get_track. No explicit when-not or alternative guidance is provided.

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