track_playlists

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

With no annotations, the description must carry the full burden. It indicates a read operation via 'Get' but does not disclose output format, authentication needs, or whether playlists are limited to owned or all playlists. Missing behavioral details like error handling or pagination.

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?

One concise sentence with no fluff. Front-loaded with the verb and resource, and the meaning is immediately clear.

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?

The tool is simple, but the description lacks critical information about the return value (playlist objects vs IDs), pagination, and any preconditions. Without output schema or annotations, the agent gets only the basic function, which might be insufficient for correct invocation or result interpretation.

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?

The description connects the single parameter trackId to 'a specific track,' giving it purpose. But it doesn't specify the ID format, source, or uniqueness. Schema has no description, so the description provides minimal but necessary 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' and identifies the resource as 'playlists that contain a specific track,' clearly distinguishing it from library_listPlaylists which lists playlists generally. The condition (contain a specific track) is explicit.

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 does not provide explicit usage guidance or alternatives. The use case is implied: when you need to find which playlists contain a track, this is the tool. However, no mention of when not to use it or how it differs from library_listPlaylists.

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