remove_from_library

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

No annotations are provided, so the description carries full burden. It mentions removal with a URI limit of 40 but doesn't disclose effects like irreversibility or return values. The output schema exists but is unexplained.

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 extremely concise, stating the purpose in a single line followed by a brief parameter explanation. No wasteful sentences; front-loaded with the action.

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?

For a simple removal tool, the description covers the core action and parameter sufficiently. It doesn't detail the output schema or mention reversibility, but the tool's simplicity makes these gaps minor.

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 0%, and the description compensates by explaining the 'uris' parameter: list of Spotify URIs with an example and maximum count. This adds crucial meaning beyond the schema's type-only definition.

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 'Remove items from the current user's library,' with a specific verb and resource. It differentiates from sibling tools like 'save_to_library' and 'remove_playlist_items' by targeting library items specifically.

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 use for removing library items but provides no explicit guidance on when to use this tool versus alternatives (e.g., 'remove_playlist_items' for playlists). It lacks when-not-to-use or prerequisite information.

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