sonarr_add

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

With no annotations, the description carries full burden. It discloses that by default it searches for missing episodes immediately, and requires user confirmation. However, it does not mention error handling, what happens if the series already exists, or auth/permissions needs. Partial transparency.

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?

Description is two sentences, front-loaded with main action, then default behavior and user confirmation requirement. No wasted 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?

Given 7 parameters, no output schema, and moderate schema coverage, the description is incomplete. It does not explain return values, error scenarios, or prerequisites (e.g., that tvdbId comes from sonarr_lookup). Important behavioral details are missing.

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 71%, so many parameter descriptions are already in the schema. The description adds no extra meaning for any parameter. Two parameters (monitored, seasonFolder) have no schema description and are not covered in the description.

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?

Description clearly states verb and resource: 'Add a series to Sonarr.' It also distinguishes from sibling lookup/search tools by specifying that this is an add operation, and includes default behavior and a usage constraint.

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?

Description mentions 'Requires user confirmation before calling' which gives a when-to-use hint, but does not explicitly state when to use this tool vs alternatives like sonarr_lookup or sonarr_search_releases. No exclusions or alternative tool names provided.

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