save_items

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action (save) but does not disclose idempotency, duplicate handling, partial failure behavior, or the exact HTTP response on success/failure. This is a significant gap for a mutation tool with zero annotation coverage.

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 sentences with no filler. It front-loads the core action ('Save one or more items') and immediately provides the key constraint (max 50). Every word earns its place, making it highly efficient.

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?

Despite no output schema and no annotations, the description covers the essential input details: accepted URI types, max items, and the target resource. For a simple one-parameter mutation, this is sufficient for an agent to invoke it correctly. Minor gaps like error handling and idempotency are not critical for a basic library-save operation.

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% and the schema already documents the 'uris' parameter with an example. The description adds value by specifying the accepted URI types (track, album, show, episode) and reinforcing the max limit of 50, going beyond the schema's generic 'Spotify URIs' description.

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 ('Save') and resource ('items to the user's library'), and enumerates the exact URI types accepted (track, album, show, episode). This clearly distinguishes it from sibling tools like remove_saved_items and check_saved_items without ambiguity.

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 implies usage (when you want to add items to the library) but does not explicitly contrast it with the complementary siblings (remove_saved_items, check_saved_items) or mention any prerequisites (e.g., authentication). It is clear enough for basic routing but lacks explicit 'when not to use' guidance.

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