export_playlist

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

With no annotations provided, the description carries the behavioral burden and does disclose important traits: it pages through every item, writes files with mode 0600 when output_path is given, and returns the document inline otherwise. It does not cover overwrite behavior or whether file writes are local, but the core behaviors are transparent.

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?

Two sentences with no filler. The core purpose is front-loaded, and the behavioral details about paging, file permissions, and inline output are packed efficiently.

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?

Given the absence of an output schema, the description reasonably explains the inline vs file-write behavior, and the schema covers all parameters. However, it does not describe what the inline document looks like, what happens after writing a file, or how max_results interacts with the promise of a 'full item list', leaving some ambiguity for agents.

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 the schema already documents all six parameters. The description adds useful meaning for output_path (write file with mode 0600 vs inline) and briefly clarifies format choices, but does not need to compensate for schema gaps.

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?

States a specific verb (Export), resource (playlist's full item list), and two concrete output formats (M3U playlist file or CSV spreadsheet). It also distinguishes itself from sibling exporters like export_playlist_markdown and export_playlist_json by naming its formats.

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?

Gives clear guidance on output_path vs inline and on M3U vs CSV formats, but does not explicitly mention when to choose this export tool over similarly named siblings such as export_playlist_markdown or export_playlist_json. The usage context is implied rather than stated as alternatives.

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