delete_series_by_id

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds no behavioral context beyond listing parameter names; it does not explain that delete_files physically removes media files or that add_import_list_exclusion prevents re-import. Thus it adds little beyond the 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 brief and avoids fluff, but it is not well-structured for an agent; it lists arguments in a raw format. The most important call-to-action (deleting) is first, but the rest is a bare enumeration. No front-loading of critical caveats.

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 optional parameters that have major side effects, this description is inadequate. It omits what happens on deletion, whether it is reversible, and the implications of the two boolean flags. The output schema exists but the description does not mention return values or confirmations. Overall, an agent cannot safely invoke this without external knowledge.

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 fully explain parameter semantics. It merely labels each parameter as 'path' or 'query' without explaining their effects. For a destructive operation, the agent cannot know that delete_files=true deletes files from disk or what add_import_list_exclusion does. This is a critical gap.

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 states 'Delete Series', which clearly identifies the verb and resource. However, it does not differentiate from the many other delete_*_by_id siblings; the agent must infer that 'series' refers to a specific TV show entity. The endpoint line adds technical detail but no semantic distinction.

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?

No guidance on when to use this tool versus alternatives like delete_series_editor or other delete operations. It does not mention prerequisites, consequences, or typical scenarios. The agent is left to guess when this is the appropriate delete method.

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