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

The description adds meaningful behavioral context beyond the annotations: deletion is conditional on an expected revision, the operation detaches content rather than destroying it, and sources, projects, and exports are preserved. It does not contradict the destructiveHint or idempotentHint annotations, though it could disclose what happens on a revision mismatch.

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 concise sentences deliver the essential action, the concurrency condition, and the preservation guarantee with no filler. The destructive scope is front-loaded, making the tool easy to scan and understand.

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?

The description gives a clear picture of what is deleted and what is preserved, and the output schema covers return values. However, with four required parameters and zero schema coverage, it does not explain idempotencyKey expectations or revision-conflict behavior, so an agent still lacks some operational details.

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 0%, so the description must compensate, but it only hints at expectedRevision via 'at an expected revision'. It does not explain seriesId, workspaceId, or idempotencyKey semantics, leaving the agent to rely on parameter names alone.

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 and resource ('Delete the Series container') and clarifies the operation's scope by stating it detaches content while preserving sources, projects, and exports. This clearly distinguishes it from sibling tools like series_get, series_list, series_content, series_apply, and series_assign.

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 when to use the tool—when deleting the container itself rather than its content—but it does not explicitly name alternatives or state when not to use it. The preservation note provides useful context but no direct routing guidance.

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