add_anime

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

There are no annotations, so the description bears the behavioral disclosure burden. It does exposed a key failure mode (no name on TVDBv2) and a workaround, but it does not describe side effects of the add operation, e.g., whether series are immediately searched, what happens on partial failure, or any permissions or storage effects beyond the root_dir parameter.

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 two sentences, front-loaded with the primary action, then followed by a specific, actionable caveat. There is no filler or repetition of schema data.

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 tool with 11 parameters, no annotations, and no output schema, more context is needed. The caveat is valuable, but the definition omits important context such as the purpose of the various booleans/defaults, how to obtain a valid anime_id, and what a successful add returns or triggers in the Medusa system.

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 for parameter meaning. It indirectly explains that anime_id is connected to the AniDB-to-TVDB mapping and that TVDB ids are found separately, but it says nothing meaningful about root_dir, status, scene, release groups, or other params. This adds a slim hint but does not compensate for 11 undocumented parameters.

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 first sentence clearly states the action ('Add an anime series'), the target system (Medusa), and the API endpoint. The note further differentiates it from the sibling add_series tool by explaining when to use the direct-series path instead.

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 an explicit fallback workflow: use search_tvdb, then add_series, when the AniDB-to-TVDB mapping fails. It does not point to other alternatives like bulk_add_anime or resolve_and_add_anime, so it stops short of full alternative routing.

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