list_series

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

Fully describes the sorting behavior (by series_index) and the purpose. No annotations provided, so the description carries full burden. It doesn't mention any destructive or side effects (none expected). Could mention that only top-level books are listed or if nested series are included, but overall good.

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?

Short and clear, front-loaded with main purpose. The example adds value but slightly increases length. Could be more concise if example removed, but it helps understanding.

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?

Given no annotations and an output schema exists, the description suffices for a straightforward list operation. Doesn't explain return format (but output schema covers that). No coverage for what constitutes a 'series' or error handling, but acceptable for a simple tool.

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 coverage is 0% (parameters not described in schema), so description must compensate. The description briefly mentions 'series_name' and 'fields' in Args, but adds no detail beyond what the parameter names imply. For example, it doesn't explain what 'fields' values are valid beyond being a list of strings.

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?

Clearly states it lists all books in a series sorted by series_index, which is a specific verb+resource+sorting detail. Distinguishes from siblings like 'get_book_info' which retrieves a single book or 'search_books' which filters by criteria.

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?

Describes when to use (to see reading order) with a concrete example. However, doesn't explicitly say when not to use or suggest alternatives like 'search_books' or 'get_book_info'.

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