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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description appropriately adds value by disclosing that the catalog is bounded, the random track is cryptographically selected, and shortest-track ties are included. It also mentions included production details, AI-involvement declarations, links, and citations.

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 compact and front-loads the return modes. It is a dense single sentence, but nearly every clause adds useful information about what the tool returns.

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?

An output schema exists and annotations cover the safety profile, so return-value detail is not strictly required in the description. However, for a four-parameter tool with 0% schema description coverage, the description is incomplete about how the parameters select modes and interact.

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 0% for four parameters, so the description must compensate. It vaguely implies album/track selection and random-track behavior but never names albumId, trackId, randomTrack, or excludeTrackIds, and gives no explanation of exclusions, precedence, or the maxItems limit.

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 that the tool returns music resources: a catalog, a selected album or track, or a random track. It specifies the resource domain and output modes, making it distinguishable from unrelated sibling tools, though it does not name a music-related alternative because none exists.

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 enumerates return modes but does not explain when to use each mode, how parameters select them, or any prerequisites. There is no explicit guidance such as using albumId for album selection or randomTrack for random selection.

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