Add books to collection

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

No annotations are provided, so the description must fully disclose behavioral traits. It usefully reveals that duplicates are ignored and cross-library books are rejected. However, it does not mention what happens on failure (e.g., invalid collection_id, non-existent items), return behavior, or whether changes are atomic. Important side effects are partially covered but not comprehensively.

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: two sentences with no wasted words. The first sentence states the primary purpose, and the second covers key edge cases. Information is front-loaded and every sentence provides value.

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 mutation tool with two parameters and no output schema, the description covers the essential behavioral constraints (duplicate handling, cross-library rejection). It implies the collection must exist and books must be of the same library. However, it does not specify the format or content of the response (e.g., success indicator, updated collection details), which would be helpful given no output schema.

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 100%, so the schema already documents both parameters. The description adds no additional semantic information about the parameters themselves; it only explains the overall behavior. Therefore, the description does not enhance parameter understanding beyond the schema.

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 uses a specific verb ('Adds') and resource ('books to an existing collection'), clearly stating the tool's function. It further distinguishes the tool from siblings like 'remove_books_from_collection' by detailing unique behaviors (ignoring duplicates, rejecting cross-library books).

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 provides clear context on when to use the tool ('Adds one or more books to an existing collection') and implies that it is safe to add duplicates because they are ignored. However, it does not explicitly name alternative tools for removal or creation, nor does it state when not to use this tool.

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