List Series

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

No annotations are provided, so the description carries full weight. 'List' implies a read-only operation and 'pagination' discloses that results are chunked. It does not describe ordering, response format, or potential rate limits, but for a simple list operation, this minimal behavioral context is adequate.

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 a single front-loaded sentence with no filler. It conveys the core action and key behavior (pagination) in six words, earning its place without redundancy.

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 two optional params and no output schema, the description provides the essential purpose and pagination behavior. However, it lacks mention of what fields each series includes, ordering, or how this differs from sibling tools like get_series or get_series_metadata, leaving some ambiguity.

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 has 0% description coverage, yet the description only says 'with pagination,' which merely hints at limit/offset without explaining their semantics or defaults. The schema already exposes the parameter names and constraints, so the description adds negligible meaning beyond what is structurally evident.

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 with pagination' clearly identifies the verb (list) and resource (series), and the pagination phrase signals a collection-oriented operation. It implicitly differentiates from sibling tools like get_series (singular) and get_series_metadata, though it does not explicitly name them.

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 implies usage when the agent needs to enumerate series, with pagination controlling result size. However, it offers no explicit when-to-use or when-not-to-use guidance, nor does it mention alternative tools for retrieving series details.

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