Add an article to a series

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

The description adds meaningful behavioral details beyond the annotations: it notes API key requirements, that adding does not change publication status or URL, that insertion shifts later articles down, and that unknown slugs cause errors. These are important operational traits not captured by the annotations alone.

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 compact, front-loaded with the core operation, and every sentence carries useful information. It covers prerequisites, identifier sourcing, optional positioning, side effects, and error behavior without redundant filler.

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 mutating relationship-assignment tool with three parameters and no output schema, this description is complete: it covers prerequisites, authentication, how to get inputs, insertion semantics, side effects, and error conditions. Nothing essential is missing.

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 100%, and the schema already provides detailed descriptions for series_slug, article_slug, and position, including the append behavior and shifting semantics. The description reinforces the same information but adds little new parameter-specific meaning beyond the schema.

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 uses a specific verb ('Place an existing article into an existing series') that clearly identifies the operation and its resources. It also distinguishes itself from creation tools by explicitly stating 'this creates neither'.

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 gives explicit when-to-use context: both the series and article must already exist. It also directs the agent to get_series and article tools for slugs, and explains the optional position behavior ('Omit position to append at the end').

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