Remove books from collection

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

The description adds value beyond the destructiveHint=true annotation by explaining exactly what happens (only membership ends, books are untouched, operation is reversible via 'add_books_to_collection'). This gives agents a clear non-destructive mental model despite the destructive annotation.

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 concise sentences with zero waste, front-loading the primary action and then clarifying the non-destructive nature in a well-structured second sentence.

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?

Given the simple input schema (2 required parameters, no output schema, no nested objects), the description is complete enough. It clearly explains the outcome and reversibility. A minor gap could be mentioning that the collection_id must exist, but this is implied by the sibling 'list_collections' tool.

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 covers 100% of parameter descriptions, so the baseline is 3. The description does not add additional parameter-specific information beyond what the schema already provides, but does not need to given full schema coverage.

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 it removes books from a collection, specifying the verb ('removes'), the resource ('books from a collection'), and distinguishes itself from deletion by clarifying that the books themselves are untouched.

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 explicitly notes when not to use this tool (if the goal is to delete books entirely) and mentions that membership can be restored with 'add_books_to_collection', providing clear context. However, it does not explicitly exclude other alternatives or mention when this tool is preferable over other collection modification tools.

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