sonarr_get_calendar

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

With no annotations, the description carries the full behavioral burden but only discloses a default window ('Defaults to the next week'), which is already implied by the schema defaults for start/end. It says nothing about read-only semantics, result limits/ordering, or what a calendar response looks like.

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?

Three short sentences, front-loaded with the core purpose and range behavior. The closing sentence is mildly promotional but costs little.

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 six-parameter, all-optional read tool with no output schema or annotations, the description covers the essential concept but omits return-shape context (what a calendar entry contains, ordering) and any note that the optional include* flags are purely additive. Adequate but with visible gaps.

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 every parameter already has a description, so the schema does the heavy lifting. The description reiterates the date-range concept but adds no meaning beyond the schema, which is the baseline-3 case.

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?

States a specific verb and resource ('Get episodes airing in a date range'), which is distinct from siblings like sonarr_get_episodes or sonarr_get_wanted because it is scoped to air dates rather than a series or a missing-episode list. It does not name those siblings explicitly, so an agent must still infer the boundary, keeping it short of a 5.

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?

'Great for seeing what's coming up' is a vague benefit statement, not guidance on when to choose this over sonarr_get_wanted or sonarr_get_episodes. No prerequisites, exclusions, or alternative-routing conditions are given.

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