unsave_tracks

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

Discloses the preview behavior and confirm flag for safety, which is crucial for a mutation tool. No annotations exist, so description carries burden well.

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?

Two sentences, no redundant text. Purpose is front-loaded, safety note is clear and brief.

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?

Covers purpose and key behavior. Output schema exists for return details. Lacks mention of prerequisites like authentication, but minor given simplicity.

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 covers 100% of parameters. Description adds value by explaining the safety mechanism (preview unless confirm=True), which goes beyond schema defaults.

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?

Clearly states verb 'Remove' and resource 'tracks from your Spotify library'. Distinguishes from sibling tools like 'save_tracks' and 'remove_tracks_from_playlist'.

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?

Provides guidance on the confirm parameter for safety, but does not explicitly contrast with alternatives like 'remove_tracks_from_playlist'.

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