export_playlist_to_csv

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

No annotations are provided, so the description must convey behavioral traits. It does not disclose whether the tool is read-only, any authentication requirements, rate limits, or limitations on playlist size. For an export tool, such details are important.

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 two sentences long, front-loads the purpose, and each sentence adds value: the first defines the action, the second suggests use cases. No redundant or unnecessary text.

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 with one required parameter and an output schema (though not detailed). The description is mostly complete given the simplicity, but could mention the CSV output structure or any limits. However, it adequately covers the main use.

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 single parameter 'playlist_id' has a schema description of 'Playlist ID', and the tool description does not add additional meaning. Since schema coverage is 100%, this score is appropriate at the baseline.

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 the specific verb 'Export' and resource 'a playlist to CSV format', clearly distinguishing it from sibling tools like 'get_playlist_tracks' (which returns tracks in a non-CSV format) or 'create_playlist'.

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 provides clear use cases: 'Great for backing up playlists or sharing song lists.' However, it does not explicitly mention when not to use this tool or compare with alternatives like 'export_review_csv'.

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