get_playlist

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

With no annotations, the description carries the full burden. It discloses the primary behavior (returns metadata and items) and adds a helpful detail ('including cover image') not present in the schema. However, it does not mention pagination behavior, error handling, or that fetch_all can retrieve up to 500 items—though those are partly covered by the schema. It is not misleading but adds limited behavioral context beyond the obvious read operation.

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 a single, front-loaded sentence that directly states the function and key included detail. There is no waste or redundancy. It is appropriately sized for a read operation.

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 description covers the essential function but is terse for a tool with pagination and a fetch_all flag. It does not specify what 'items' contains (e.g., full track objects vs. IDs) or elaborate on the metadata structure, and there is no output schema to compensate. An agent might need to infer item format. It is adequate but not fully complete.

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 100%, so all four parameters (id, limit, offset, fetch_all) are already documented. The description only implies that limit/offset/fetch_all apply to items, but does not add semantic detail beyond the schema. This meets the baseline but adds no extra value.

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 specific verb ('Get'), a specific resource ('a playlist'), and the precise output ('metadata (including cover image) and items'). It clearly distinguishes from sibling tools like get_playlist_cover (which only fetches cover) and get_user_playlists (which lists user's playlists), making its purpose unambiguous.

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 implies usage (when you need playlist metadata and items) but does not explicitly state when to use this instead of alternatives like get_playlist_cover or get_user_playlists. There are no exclusions or when-not-to-use guidance. The context is clear enough for an agent to infer, but it lacks explicit routing.

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