itunes_get_playlist_tracks

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

With no annotations provided, the description carries the full burden and does disclose the output format ("newline-separated list ... formatted as 'Track Name - Artist'"), which is genuinely useful behavioral info. However, it remains silent on edge cases like empty playlists or non-existent playlists, which a getter tool could reasonably be expected to handle.

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 efficiently structured with a one-line purpose followed by standard Args and Returns sections. Every line earns its place, and the format is scannable, though the docstring style is slightly verbose for a single parameter.

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 getter tool with one string parameter and no output schema or annotations, the description covers the essential contract: what it takes as input and the exact format of the return value. There's little ambiguity in what the tool offers, making it appropriately complete for its complexity.

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 schema provides zero description coverage for the single `playlist` parameter, so the burden falls on the description. The Args section compensates by documenting it as "The name of the playlist to inspect." This is exactly the kind of compensation the rubric calls for, though it lacks examples or default values.

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 opening line "Get all tracks in a named playlist" uses a clear verb (Get) with a specific resource (tracks in a named playlist). It clearly describes the action but doesn't distinguish it from siblings like itunes_export_playlist or itunes_get_track_metadata, so a point is lost for missing sibling differentiation.

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?

Usage is implied through the structure ("Get all tracks in a named playlist") and the Args section, and the name `playlist` suggests the prerequisite of having a playlist name. However, there's no explicit when-to-use guidance or exclusions pointing to alternatives like itunes_list_playlists or itunes_export_playlist, so the usage is implied but not explicit.

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