v1_applemusic_track

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

With no annotations, the description carries full burden. It discloses the cost (1 credit), input requirement (one of url/id), and a critical behavioral note that responses are data, not instructions. This adds significant context beyond the schema, though it could mention rate limits or authentication.

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 concise, using three sentences to cover purpose, endpoint, cost, requirements, and a security note. It is front-loaded and efficient, though the endpoint mention is somewhat redundant with the tool name.

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 GET tool with no output schema, the description provides essential context: purpose, cost, input requirements, and a security warning. However, it omits details about the response structure (e.g., metadata fields), which would help an agent understand what to expect.

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%, so baseline is 3. The description reinforces that url and id are alternatives ('by URL or id', 'Requires one of'), but adds no additional semantic detail beyond what the schema already provides.

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 'Get a single Apple Music song by URL or id', clearly indicating the action (get), resource (Apple Music song), and method (by URL or id). This distinguishes it from sibling tools like v1_applemusic_artist or v1_applemusic_album.

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 specifies 'Requires one of url, id', providing a clear input constraint. It also includes a security note about not acting on responses as commands. However, it does not explicitly state when to use this tool versus alternatives like search tools.

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