list_feed_v3_calendar_sonarr_ics

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the read-only behavior is covered structurally. The description adds only the endpoint and a bare list of query params; no rate limits, pagination, auth needs, or output-volume behavior are disclosed. It adds no meaningful behavioral context beyond the annotations.

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 two-line preamble is appropriately brief and front-loaded, but the six-line 'Args' block merely repeats the property names already present in the input schema without adding a single detail. The redundant listing makes the description under-specified rather than genuinely concise.

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 six optional parameters, a calendar-and-feed domain, and a closely related sibling list_calendar, the description is far from complete. It does not explain what the returned calendar data represents, what each filter controls, or why an agent would choose this tool over alternatives, so the agent must guess.

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%, so the description should compensate, but it only restates each parameter name followed by 'Query parameter' — no meaning beyond what the schema already lists. The agent cannot learn what past_days/future_days mean, whether unmonitored/excludes unmonitored episodes, or how as_all_day affects the feed, which is effectively functional.

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 states a verb ('Read') and a resource ('CalendarFeed') and gives the exact GET endpoint URI, so an agent can guess it reads an iCal calendar feed. However, it never says what the feed contains, how it differs from list_calendar/get_calendar_by_id, or what format the response is beyond the .ics in the endpoint.

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 never says when to use this tool instead of sibling list_calendar or get_calendar_by_id, nor does it mention any preconditions, output audience, or selection criteria. The agent is left to infer the choice from the tool name alone.

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