add_anime

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

No annotations are provided, so the description must fully disclose behavioral traits. It discloses a potential failure mode and the underlying ID mapping issue. However, it does not mention side effects, required permissions, reversibility, or the fact that it modifies the Medusa database. The transparency is moderate.

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 concise with two short paragraphs. The first sentence clearly states the purpose. The second paragraph adds useful contextual information without fluff. No redundancy or unnecessary words.

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 tool has 11 parameters with no schema descriptions, no output schema, and moderate complexity. The description only covers the basic purpose and one failure scenario. It lacks explanations for parameters, required inputs, output format, and other important behavioral details. It is incomplete for an agent to use effectively.

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% for 11 parameters. The description adds no meaning beyond the schema; it does not explain any parameter's purpose, format, or expected values. For example, it does not clarify that anime_id is an AniDB ID or what root_dir should contain. This severely limits the agent's ability to correctly invoke the tool.

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 an anime series to Medusa via a specific API endpoint. It provides a clear verb-resource pairing. However, it does not explicitly differentiate from sibling tools like add_series or bulk_add_anime, though it hints at a workaround involving add_series.

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 explicitly mentions a known failure case ('no name on TVDBv2') and provides a concrete workaround: use search_tvdb to find the correct TVDB ID, then add_series to add it directly. This gives clear guidance on when this tool might fail and what alternative to use. It could be more comprehensive but is still helpful.

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