sonarr_get_wanted_missing

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

With no annotations provided, the description carries the full burden. It states the core behavior (listing missing monitored episodes) but does not disclose any additional behavioral traits such as sorting, default pagination semantics, or that it is read-only. The 'Get' verb implies a read operation, but more detail (e.g., that it only includes episodes with airdate in the past) would enhance 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?

The description is a single, front-loaded sentence with no unnecessary words. It clearly conveys the essential purpose without redundancy, earning a top score for conciseness.

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 simple paginated list tool with no output schema and no annotations, the description covers the core purpose and pagination. It does not explicitly mention return fields or sorting, but for a basic lookup, it is sufficiently complete. Slightly more detail about what 'missing' means in a Sonarr context would make it fully explicit.

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 coverage is 100%, and the schema already provides descriptions for page and pageSize. The description only hints at pagination via 'paginated', adding no extra meaning beyond what the schema documents. This matches the baseline of 3.

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 specific verb ('Get') and resource ('paginated list of monitored episodes that are missing'), and clarifies the meaning of 'missing' as 'not yet downloaded'. This clearly distinguishes it from sibling tools like sonarr_get_wanted_cutoff, which targets cutoff-unmet episodes.

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 does not explicitly state when to use this tool versus alternatives like sonarr_get_wanted_cutoff or sonarr_search_missing. However, the wording 'missing (not yet downloaded)' implies its purpose, giving reasonable context without explicit exclusions.

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