Sonarr Get Cutoff Unmet

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

No annotations are provided, so the description carries full burden. It only states the basic function without disclosing behavioral traits such as pagination, authentication needs, or side effects (e.g., read-only nature). The description lacks the behavioral context needed for an agent to use it safely.

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, concise sentence. While efficient, it lacks structure for a tool with 10 optional parameters. A more structured description with parameter roles would be beneficial without adding excessive length.

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 the tool has 10 parameters, no output schema, and no annotations, the description is incomplete. It does not explain pagination, filtering, or result format, making it difficult for an agent to invoke the tool correctly. The description needs to cover these aspects to be contextually complete.

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?

The input schema has 10 parameters with 0% schema description coverage. The description adds no meaning to any parameter, leaving their purpose entirely unclear. For example, 'to', 'from', 'page', 'cursor', etc., are not explained. The description fails to compensate for the lack of schema descriptions.

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 'List Sonarr episodes that have not met cutoff' uses a specific verb ('list') and resource ('episodes that have not met cutoff'), clearly distinguishing it from sibling tools like sonarr_get_episodes (all episodes) and sonarr_get_missing (missing 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 implies the tool is for listing cutoff-unmet episodes, which provides context. However, it does not explicitly state when to use this vs. alternatives like sonarr_get_episodes or sonarr_get_missing, nor does it mention prerequisites or exclusions.

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