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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds behavioral nuance by restricting the tool to public tracks and specifying lookup keys, but it does not detail response behavior or error cases. Given that annotations carry the safety burden, the description's added context merits a 3, not lower.

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 tight sentences with no filler. The primary use case is front-loaded, and the cautionary note is appended without bloat. Every word contributes to the agent's understanding.

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?

With only one parameter, a clear purpose, an output schema for return value structure, and annotations covering safety, the description is sufficient. The agent has everything needed to select and invoke the tool correctly. No critical gaps remain.

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%, so the description must compensate. It does by clarifying that the single required 'id' parameter can be either a blob identifier or a title. This directly adds meaning beyond the raw schema field. The guidance is a bit ambiguous about whether both types are accepted interchangeably, but it still provides essential semantic context.

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'), identifies the resource ('one public track'), and specifies the lookup methods ('by blob identifier or title'). It clearly distinguishes this tool from sibling tools like get_composition or get_release by emphasizing 'public track' — an agent can tell what it does without needing to inspect the schema.

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 states when to use the tool ('Use this when an agent needs to get one public track...') and provides an important exclusion ('Do not infer ownership, licensing, or unpublished availability'). It does not explicitly name an alternative tool, but the boundary condition ('public') implies when not to use it, leaving little ambiguity.

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