bookshelf_add_books_to_shelf

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

Annotations already indicate a non-read-only, non-destructive operation. The description adds no additional behavioral details such as idempotency, duplicate handling, or side effects. It merely repeats the action implied by the tool name and annotations.

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, front-loaded with the core purpose and followed by a necessary body hint. Both sentences earn their place with no redundancy or irrelevant detail.

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?

The tool has a nested body with no schema property descriptions, and the output schema exists but does not compensate for input ambiguity. The description provides only minimal field names, insufficient for an agent to correctly invoke the tool without additional inference.

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?

With 0% schema description coverage and no property definitions, the description carries the burden of explaining the body. It names 'bookshelfId' and 'bookIds' but fails to specify types, requiredness, or structure, leaving significant ambiguity for constructing a valid request.

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 ('Add the given books') and the resource ('to a Goodreads/Hardcover shelf'), which distinguishes it from sibling tools. The mention of the body as BookshelfResource further clarifies the operation.

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 when to use the tool (when adding books to a shelf) but provides no explicit alternatives or exclusion criteria. There is no guidance on when not to use it or how it differs from potentially similar actions.

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