Sonarr Get Missing

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

With no annotations, the description must disclose behavioral traits. It only states 'list,' ignoring details like pagination support (cursor, page, limit), default sorting, or whether the operation is read-only. The numerous schema parameters suggest complex behavior, but the description fails to explain it.

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 extremely short but at the expense of utility. It omits essential context for a tool with 10 parameters and many siblings. Conciseness should not sacrifice necessary information.

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 no output schema, high parameter count (10), 0% parameter descriptions, and numerous sibling tools, the description is severely incomplete. It provides almost no context for correct usage, failing to address filtering, pagination, or expected response structure.

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%, yet the description adds no parameter explanations. All 10 parameters (page, limit, cursor, detail, fields, etc.) remain undocumented in both schema and description, making correct invocation nearly impossible.

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 uses a clear verb 'List' and specifies the resource as 'missing Sonarr episodes,' which is informative. However, it does not differentiate from sibling tools like 'sonarr_get_cutoff_unmet' or 'radarr_get_missing,' missing an opportunity to clarify unique scope.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites, typical use cases, or conditions where other tools might be preferred, leaving the agent without decision support.

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