add_series

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

No annotations are provided, so the description carries the burden. It mentions the endpoint and that quality values default to global settings, but does not discuss side effects (e.g., overwriting existing series), authentication needs, or rate limits. Some context is added, but not exhaustive.

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 front-loaded with the core action, then provides usage context, then lists quality values. It is reasonably concise, though the quality list is lengthy. No unnecessary sentences.

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?

Given 10 parameters, no output schema, and no annotations, the description should explain more than just the quality values. It fails to describe the purpose of required parameters (tvdb_id, root_dir) or the effect of boolean flags like anime and paused. The return value is not mentioned.

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 should compensate. However, it only explains the quality parameter values, leaving the other 8+ parameters undocumented. This is insufficient for an agent to correctly set parameters like anime, scene, or language.

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 clearly states the tool adds a series to Medusa using a TVDB ID via a specific endpoint, distinguishing it from add_anime by noting it is a fallback that bypasses anime resolution.

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?

Explicitly says to use this tool as a fallback when add_anime fails, and instructs to first find the TVDB ID with search_tvdb. This differentiates it from sibling tools and provides clear when-to-use guidance.

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