export_snapshot_bundle

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

With no annotations provided, the description must carry the behavioral burden. It mentions 'export file locally' and 'dry_run=true (default) previews the bundle', which implies a write operation with a dry-run mode. However, it does not disclose potential side effects like overwriting existing files, output location, or what the committed action returns. This is somewhat adequate but incomplete.

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 one sentence with a semicolon separating the core action from the dry_run clarification. It is front-loaded with the primary purpose and avoids redundancy. Slightly dense but efficient and readable.

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 schema describes all four parameters fully and there is no output schema to explain, the description provides sufficient detail for an agent to call the tool correctly: it covers selection and the dry_run default. It doesn't explain the 'locally' write destination or behavior when committed, but these are minor gaps given the schema.

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 coverage is 100%, so parameters are already documented. The description adds valuable context by explaining that 'playlist' bundles all snapshots of a playlist and 'snapshots' are explicit ids, implying an override relationship. This goes beyond the schema descriptions and helps an agent choose between them.

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 ('Bundle') and resource ('snapshots') and clarifies the selection modes ('all of one playlist, or explicit ids'), which clearly distinguishes this from other export/snapshot tools. It is unambiguous about what the tool does.

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?

No guidance is given on when to use this tool versus other export tools (e.g., export_library_json, export_all_playlists, sidecar_export_bundle) or when not to use it. The description only states what it does, leaving the choice to the agent without explicit alternatives or exclusions.

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