Get series

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

Annotations already declare readOnlyHint=true, so the agent knows it's safe. The description adds that the tool returns books, which is a behavioral trait beyond the annotation. However, it does not mention the 'detail' parameter's impact on response size or other potential behaviors like auth requirements, but the annotation covers the safety aspect.

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 sentences, front-loaded with the primary purpose, and a second sentence for the alternative use case. No redundant or unnecessary words. Every sentence earns its place.

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 output schema, the description conveys the core behavior (fetches a single series with books) and provides sibling guidance. It lacks explicit mention of return format or error handling, but the schema covers parameters. For a simple read tool with annotations, this is reasonably complete.

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% with both parameters well-described (series_id: required, string; detail: enum with compact/full and explanation). The tool description itself does not add any parameter semantics beyond what the schema provides. Baseline 3 is appropriate for high coverage.

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 explicitly states the action ('fetches'), the resource ('a single series by id'), and the result ('including its books'). It also distinguishes from the sibling tool 'list_library_items' by specifying the alternative use case, which clarifies the tool's unique role.

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 provides clear guidance: use this tool to fetch a single series by ID, and for listing with paging and sorting, use 'list_library_items' with filter_group='series'. This directly addresses when to use and when to avoid, with an explicit alternative.

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