List series

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

Annotations provide readOnlyHint=true. The description adds that the tool returns number of books and total duration per series, and warns that the 'full' detail option returns very large data. It does not mention pagination or sorting behavior, but these are covered in the schema. No contradictions.

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 short, front-loaded sentences. The first sentence immediately states the core purpose and output summary. The second sentence provides critical usage guidance. No wasted words.

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 6 parameters including pagination and sorting, but no output schema. The description mentions the returned fields for series (number of books, total duration) and warns about the full detail size, which compensates somewhat for missing output schema. It does not describe pagination details or sorting keys, but the schema provides that. The sibling guidance adds completeness. Overall, adequate but could be more thorough.

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 a baseline of 3 applies. The description does not add new meaning to any parameter beyond what the schema already provides (e.g., page, sort, limit, detail, descending, library_id). No additional context is given for parameters.

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 verb 'Lists' and the resource 'series of a book library', and adds specific output fields (number of books, total duration). It distinguishes from siblings by directing agents to list_library_items for listing books of a single series, and the sibling list includes get_series for a single series.

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 tells when not to use this tool for listing books of one series and provides the correct alternative call with parameters. This is a direct, helpful usage guideline that prevents misuse.

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