Create a series

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

Discloses required API key, the public URL side effect, and that the series remains empty until articles are added. Also mentions the return value includes the slug needed by add_to_series, covering side effects and return behavior beyond annotations.

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 three sentences, each serving a distinct purpose: definition, usage guidance, and side effects/return. No redundant information or fluff.

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 the schema covers parameter definitions, the description augments with usage preconditions, side effects, and return value expectations, providing a complete context for using the 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?

The schema already provides complete descriptions for both parameters (title and description), including that the slug is derived from title. The tool description adds no extra parameter-specific details, so it remains at the baseline for full schema 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 clearly states the tool creates a new, empty series, which is a named collection for articles. It distinguishes itself from sibling tools like add_to_series and get_series by focusing on the creation aspect.

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?

Explicitly advises calling get_series first to avoid duplicate series, and notes that each call creates a new series without deduplication. This gives clear when-to-use and when-not-to-use guidance.

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