itunes_duplicate_playlist

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

No annotations are provided, so the description must disclose behavior. It implies a non-destructive creation of a new playlist, but does not explicitly mention side effects, prerequisites (e.g., source playlist existence), or whether all tracks/metadata are copied.

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 a single, concise sentence that fully captures the tool's purpose without extraneous detail.

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 description is adequate for a simple duplicate operation, but it lacks details such as return values, error conditions, or specific behaviors (e.g., whether the new playlist is empty or contains all tracks). Given the lack of annotations and output schema, this minimal information may be insufficient for full context.

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 description indirectly refers to the parameters by mentioning 'existing playlist' and 'new playlist', but does not explicitly define them. The parameter names are self-explanatory, but the description adds minimal clarification beyond what the names imply.

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 the action (duplicate/clone) and the resource (playlist), distinguishing it from other playlist operations. It is specific and unambiguous.

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 only states what the tool does, but does not provide explicit guidance on when to use it versus alternatives like create_playlist or merge_playlists. No conditions or exclusions are mentioned.

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