get_lyrics

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

With no annotations and no output schema, the description carries the behavioral burden. It does disclose the external source and the conditional 'if available' behavior for synced lyrics. However, it omits details about failures, unsynced fallback, rate limits, or any payload structure beyond the synced-lyrics mention.

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?

Two short sentences deliver the core action, the source, and the primary return caveat with no redundant words. The most important information is front-loaded.

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 two-parameter lookup tool, the description covers the source, what it returns, and the main conditional (synced lyrics if available). Since there is no output schema, stating the return value is important and is handled, though minor gaps like unspecified no-result behavior prevent a perfect score.

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 description coverage is 100%, and both track_name and artist_name are self-explanatory in the schema. The description adds no extra guidance about parameter format, escaping, or how strict the matching is, so it neither improves nor degrades the schema's clarity.

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 uses a specific verb ('Get') with a clear resource ('lyrics for a track') and identifies the data source (LRCLIB). This makes it immediately distinguishable from siblings like search_lyrics, which implies finding rather than exact lookup.

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 intended use is implied: given a track_name and artist_name, retrieve lyrics. However, the description does not explicitly state when to use this over search_lyrics, nor does it mention conditions or exclusions such as requiring exact artist/track names or preferring search_lyrics when the track is unknown.

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