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

The annotations already disclose that this is a read-only, idempotent, non-open-world operation. The description adds the non-obvious fact that it returns a playable song card 'where the client supports MCP Apps', which is useful conditional behavior. Beyond that, it does not describe error cases, missing-field behavior, or output shape.

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?

A single compact sentence grouping return fields, followed by one clarifying sentence about the song card. Front-loaded and efficient; slightly dense with the list of returns, but no wasted words.

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 one-parameter read-only tool with full schema coverage and annotations, the description is adequate. However, it leaves the agent guessing how it relates to the four overlapping siblings, and the conditional song-card behavior could be clearer about when it applies.

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% with the slug parameter fully documented, including an example and an enum of valid values. The description adds nothing about the parameter, so the baseline 3 is appropriate.

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 clear verb+resource ('One Boots & Bassline song') and enumerates what it returns (about, audience, lyrics, preview, streaming links). It does not differentiate itself from siblings like find_song, get_lyrics, or get_listening_links, which overlap significantly.

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 use this tool versus find_song, get_lyrics, or get_listening_links. The agent is left to infer that this is a general-purpose detail fetch, but the overlapping siblings make that inference risky.

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