sonarr_list_release

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

The readOnlyHint annotation already indicates a read-only operation, but the description adds no further behavioral context. It does not mention what data is returned, how parameters affect results, or any side effects. The description is consistent with the annotation but contributes nothing beyond 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 this is under-specification rather than effective conciseness. It consists of two words that merely echo the tool name, wasting the opportunity to convey useful information. A concise description should still include essential meaning, which is absent here.

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 three optional parameters, an output schema, and a readOnly annotation, the description provides an inadequate level of context. It fails to explain what 'releases' refers to, how the filters work, or what the output represents. This is insufficient for an agent to correctly select and invoke the tool.

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% and the description does not explain any of the three parameters (series_id, episode_id, season_number). The schema itself provides only names with no descriptions, so the tool is entirely opaque regarding parameter semantics. The description fails to compensate for this gap.

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 release' is essentially a restatement of the tool name 'sonarr_list_release' with minimal grammatical adjustment. It identifies a verb and resource but omits any scope or distinguishing features, such as what kind of releases are listed or how they are filtered. It also fails to differentiate from sibling tools like sonarr_search_releases.

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 usage guidance is provided. The description offers no indication of when to use this tool versus alternatives like sonarr_search_releases or sonarr_list_releaseprofile, nor any prefilters or prerequisites. The absence of any context or exclusions leaves the agent without clear direction.

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