Remove Saved Audiobooks

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

The annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one genuinely new behavioral fact: a batch cap of 50 IDs per call. It does not disclose what happens when an ID is invalid or not saved (silent skip vs. error), nor the auth scope required for a destructive library mutation.

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?

One sentence of purpose followed by a single Args block with no filler; the destructive nature of the operation and the batch limit are both surfaced up front. The docstring-style Args heading is slightly redundant with the schema but costs almost nothing.

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 single-parameter tool with an output schema, the description covers what is removed and the batch limit, so the minimum is met. It omits partial-failure semantics and irreversibility, which matter for a destructiveHint mutation, leaving real gaps for an agent deciding how to call it safely.

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%, so the description must carry the parameter meaning, and it does: it tells the agent the array accepts either bare audiobook IDs or URIs and is capped at 50 entries. That is meaningfully more than the schema, which only says 'array of strings.' It lacks format specifics or examples, which keeps it below a 5.

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?

States a specific verb and resource: 'Remove audiobooks from the user's library.' An agent can immediately distinguish this from save_audiobooks, get_saved_audiobooks, and check_saved_audiobooks. It stops short of explicitly differentiating itself from the parallel remove_saved_albums / remove_saved_shows / remove_saved_tracks siblings, though the resource name does that implicitly.

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 when-to-use or when-not-to-use guidance, no mention of alternatives such as save_audiobooks or check_saved_audiobooks, and no statement of prerequisites (e.g. the item must currently be saved). Usage is only implied by the tool name and the phrase 'from the user's library.'

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