sonarr_get_calendar

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it returns upcoming air dates but does not describe the response format (e.g., list of episodes, fields included), whether it is read-only, or any limitations such as maximum days. The read-only nature is inferred but not explicit.

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 that efficiently conveys the tool's purpose. There is no wasted wording; every part ('Get upcoming episode air dates') is meaningful, and 'from Sonarr' is mildly redundant but not detrimental.

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 tool with one optional parameter and no output schema, the description is minimally adequate but lacks some context that would help the agent fully understand the result. It does not explicitly mention the 'days' parameter or the nature of the returned data (e.g., whether it includes show names and episode numbers). The description would benefit from mentioning the default timeframe and that it returns a list of episodes.

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 schema covers 100% of the parameters, with the 'days' parameter already described in the schema as 'Days to look ahead (default: 7)'. The description adds no additional parameter semantics beyond what the schema provides, so the baseline of 3 applies.

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 clearly states a specific verb ('Get') and resource ('upcoming episode air dates'), which precisely distinguishes this calendar tool from the many other Sonarr tools in the sibling list. No other tool seems to serve the same purpose, so there is no ambiguity.

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?

There is no guidance on when to use this tool versus alternatives such as sonarr_get_episodes or sonarr_search. It does not state whether it covers all series or requires filtering, nor does it mention any prerequisites or exclusions. The usage context is only implied by the term 'upcoming'.

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