ical_list_feeds

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

With no annotations provided, the description carries the full burden and uses it well: it explicitly states that feeds are read-only and explains why (.ics is an HTTP-served file with no write protocol). This reassures the agent that the tool never mutates anything, adding meaningful behavioral context beyond the name.

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 short sentences: the first delivers the core purpose, the second adds the key behavioral constraint. No filler, no redundancy, and the most important information is front-loaded.

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 zero-parameter, read-only list tool, the description is nearly complete: it states the resource, its source, and its read-only nature. It omits an explicit statement of the return format, but the absence of an output schema and the trivial complexity make this a minor gap rather than a critical one.

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 tool has zero parameters and an empty input schema, so the description has no parameter burden to carry. Baseline for 0 params is 4; the description appropriately adds no irrelevant parameter detail.

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 clear verb ('List') and resource ('subscribed iCal feeds') with a precise source location ('accounts.json under "calendarFeeds"'). This unambiguously distinguishes the tool from siblings like ical_list_events (events vs feeds) and calendar_list_calendars (Google Calendars vs iCal subscriptions).

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 when to use the tool—when you need to see subscribed iCal feeds—but does not explicitly name alternatives or state when not to use it. The read-only note hints that this tool is for inspection only, but no exclusion or routing guidance is provided for the closely related ical_list_events or calendar_list_calendars.

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