sonarr_get_calendar

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

Annotations already declare readOnlyHint=true, and the description's 'Fetch' aligns with that. The description adds the 'upcoming' scope, which is useful context, but it does not describe the return format, error behavior, or any other behavioral details beyond the annotation.

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, focused sentence with no redundant words. It conveys the essential action and scope efficiently.

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 simple get-by-id nature, the description is somewhat adequate, but the ambiguity of 'id' and the lack of clarity about what constitutes an 'upcoming episode calendar' leave gaps. Output schema and annotations cover some context, but the description itself is minimal.

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% for the 'id' parameter, and the description only says 'by id' without explaining what the id refers to (e.g., episode id, calendar entry id). This fails to compensate for the lack of parameter documentation.

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 the tool fetches a single upcoming episode calendar by id. It uses a specific verb (Fetch) and resource (single upcoming episode calendar), and the 'single' and 'by id' distinguish it from the sibling tool sonarr_list_calendar.

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 usage: use when you have an id for a specific calendar entry. It does not explicitly mention alternatives or when not to use, but the 'by id' scope provides clear context without needing exclusions.

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