itunes_export_playlist

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

With no annotations, the description must disclose behavioral traits, but it only states the core export action. It does not clarify whether the tool returns the exported data, writes to a file, or behaves when the playlist is missing. The read-only nature and side effects are absent.

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 extremely concise: a single purpose statement followed by a compact parameter list. Every word earns its place, with no unnecessary filler.

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 two-parameter tool, it covers the core action and parameter semantics, but it lacks details about the return value or output format behavior (e.g., whether data is returned directly or saved to a file), and does not address error scenarios. It is adequate but has clear gaps.

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?

Despite 0% schema description coverage, the description explains both parameters clearly: playlist is 'the name of the playlist to export' and format lists the allowed values 'json', 'csv', or 'markdown' with a default. This adds significant meaning beyond the bare schema.

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 clearly states 'Export all tracks in a named playlist to JSON, CSV, or Markdown' with a specific verb and resource, and the format options distinguish it from sibling tools like itunes_get_playlist_tracks which would simply retrieve tracks.

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?

There is no explicit guidance on when to use this tool versus alternatives. It only lists parameters, with no mention of use cases, exclusions, or comparison to related tools like itunes_get_playlist_tracks or itunes_add_to_playlist.

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