add_to_playlist

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

With no annotations, the description carries the full behavioral burden. It only discloses the 100-URI limit, but does not state that this is a mutation, any auth requirements, error behavior on invalid playlist/URIs, or idempotency. 'Add' implies a write, but side effects are not described.

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 short sentences that front-load the action and the key constraint. Every word earns its place; it is appropriately sized for a simple add operation.

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 minimal and lacks context about side effects, requirements, and expected outcomes. No output schema exists, and the description does not explain success/failure behavior, making it incomplete for an agent performing a mutation.

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 input schema already documents all three parameters with descriptions, and the description only repeats the limit already in the schema (maxItems). It adds no further semantics about URI format, deduplication, or interaction with the position parameter beyond what the schema provides.

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 and resource ('Add tracks or episodes to a playlist') and adds the 'Max 100 URIs per call' qualifier. It clearly distinguishes from siblings like remove_from_playlist, update_playlist, and create_playlist. The purpose is 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?

No guidance on when to use this tool versus alternatives such as add_to_queue or save_items. The description does not mention prerequisites (e.g., playlist must exist) or any explicit conditions for choosing this tool over others.

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