bookshelf_list_series

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

The readOnlyHint annotation already discloses that this is a read-only operation. The description adds no behavioral context—no mention of default behavior, filtering results, pagination, or what constitutes a 'series'. It does not contradict the annotation but contributes nothing beyond it.

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 extremely brief—'List series. Query params: authorId.'—but this brevity is under-specification rather than conciseness. Most of it restates the tool name and schema, adding minimal information.

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 list tool with one optional parameter and an output schema, the description is still incomplete. It doesn't explain the concept of 'series' in this context, the effect of the author filter, or any limitations. The output schema may cover return values, but the description provides insufficient guidance for tool selection and invocation.

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 description mentions 'authorId' but the actual schema parameter is 'author_id' (snake_case), creating potential ambiguity. It does not explain whether the parameter is optional (it has a default and is not required), what happens if omitted, or how it filters the list. Schema coverage is 0%, and the description fails to compensate.

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 'List series' clearly identifies the action (list) and resource (series), distinguishing it from sibling list_* tools like list_author. However, it lacks any additional scope or context beyond the resource name.

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?

No guidance is provided on when to use this tool versus alternatives, nor any exclusions. The description does not mention any scenarios, prerequisites, or relationship to other series-related tools.

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