delete_series_editor

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered outside the description. However, the description adds no behavioral context beyond that: it does not say what gets destroyed, whether the operation is reversible, whether any related resources are affected, or what happens when the body is null. The note to read the schema is about request construction, not runtime behavior.

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 short and front-loaded with the operation, which is good. But 'Delete SeriesEditor.' essentially restates the tool name, and the explicit DELETE URL is redundant with the description. The brevity is not a virtue here because the remaining text provides little new information.

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 destructive tool with a free-form body parameter and no parameter documentation, the description is incomplete. It fails to explain what the SeriesEditor resource is, what the body should contain, how to distinguish this from related delete tools, or what the matching GET/schema endpoint actually is. The presence of an output schema helps for return values but not for understanding the request payload.

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 bears the burden of explaining the body parameter. It only says 'Request payload' and tells the agent to read a GET or schema endpoint first, without listing any fields or indicating what the payload should contain. That is useful procedural direction but not substantive parameter semantics, especially since no matching get_series_editor or list_series_editor_schema tool appears among the siblings.

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 provides a clear verb and resource ('Delete SeriesEditor') and the HTTP endpoint, so it is more than a pure tautology. However, 'SeriesEditor' is never explained, and the description mostly restates the tool name. An agent cannot tell whether this deletes a single series, a bulk editing selection, or some other entity without additional context.

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?

There is no guidance about when to use this tool instead of delete_series_by_id, delete_episodefile_bulk, or update_series_editor. The only procedural note, 'Read the matching GET or the /schema endpoint first,' concerns payload discovery rather than tool selection. No alternatives or exclusion conditions are mentioned.

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