list_calendar_subscriptions

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

With no annotations, the description carries the full burden. It discloses one real behavioral trait — the web-mode-only restriction — and "Lists" implies a non-mutating read, but it says nothing about pagination, ordering, result size, or auth. For a zero-parameter tool this is thin but not empty.

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 with the resource named first and the mode constraint immediately after. No filler, no restatement of the title, nothing to trim.

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 trivial zero-param list tool this is minimally adequate, but with no output schema and no annotations an agent still does not know what a "calendar subscription" object contains or whether results are paged. The web-only note partially offsets this but does not close the gap.

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 takes no parameters, so per the baseline rule the schema does the heavy lifting and no parameter explanation is required. There is simply nothing for the description to clarify here.

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 specific verb and resource ("Lists calendar subscriptions"), which cleanly separates it from siblings such as list_calendar_accounts and list_calendar_events. It does not explicitly call out the differentiation, but the resource is specific enough that an agent can route to it without ambiguity.

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?

"Web mode only" is a genuine eligibility constraint that tells the agent when this tool is callable, which is more than no guidance. However, it names no alternatives and gives no conditions for choosing between this and the other list_* siblings, leaving usage largely implied.

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