get_calendar

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the core listing behavior and adds a genuinely useful server-side default for the date range. However, it does not describe the default summary output shape or how the return varies with the detailed/include flags, leaving those details to the schema.

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?

Two sentences with no filler; the action and scope are front-loaded, and the default date behavior earns its place as the second sentence. Very easy to scan.

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 read-only listing tool with zero required parameters and a fully documented schema, the description conveys purpose and the key default. Since there is no output schema, a brief note about the default response shape would make it fully complete, but the current definition is still sufficient for correct invocation.

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 has a meaningful description, so the baseline is 3. The description adds the key semantic that omitting start/end defaults to today/tomorrow on the Sonarr side, which is not captured in the schema.

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?

Opens with a specific verb and resource ('List episodes') and scopes it to date range, with 'what aired recently and what is coming up' clarifying the calendar role. This clearly distinguishes it from the episode lookup/list tools among the siblings.

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?

Provides clear context for when to use the tool: it is the calendar/date-range airing query, and the today/tomorrow default is useful operational guidance. It does not explicitly name alternatives or exclusions, so it stops short of the strongest routing guidance.

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