List series

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

Without annotations, the description discloses that results are paginated and each series includes book/read counts and authors. This covers key response behavior for a simple read operation, though it doesn't mention authentication or error scenarios.

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 concise, front-loaded sentences: the first states the core purpose and output content, the second provides a clear follow-up action. 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?

For a simple paginated list with two optional well-documented parameters and no output schema, the description adequately explains what is returned and how to progress to get_series_books, making it complete for an agent.

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 already fully documents page and size with defaults and constraints, and the description adds no additional parameter meaning beyond referencing pagination, so the schema carries the baseline weight.

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 tool lists the library's series with specific details (book/read counts and authors) and distinguishes it from sibling tools like get_series_books and list_authors.

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?

It gives actionable guidance to use the returned series id with get_series_books for reading books in a series, but does not explicitly exclude alternatives or mention when not to use the tool.

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