series_books

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

Adds behavioral detail beyond annotations: pagination in batches, limit capped at 100, and semantics of returned fields (placement and is_primary). No contradiction with readOnly/idempotent 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?

Two compact paragraphs, front-loaded with the core action and structured with parameter guidance and output details. No filler or redundant repetition of annotations.

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 description covers purpose, disambiguation, output field semantics, and pagination constraints. With the output schema available and read-only annotations, an agent has everything needed to call the tool correctly.

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 has 0% description coverage, but the description explains all three parameters: book_id is the input book in the series, series_index is zero-based and references get_book's series_memberships order, and limit is capped at 100. This fully compensates for the schema gap.

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 the precise verb 'List' with resource 'books in a series' and a distinguishing attribute: reading-order placement. Clearly distinguishes from sibling tools like author_books and similar_books by focusing on a given book's series membership.

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?

Explains when to use it: given any book in a series, list its books; also gives a specific conditional: when a book belongs to multiple series, pass the zero-based series_index from get_book's series_memberships order. Does not explicitly rule out alternatives but provides clear context and a concrete workflow referencing get_book.

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