list_calendars

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

Annotations already declare readOnlyHint=true. The description adds behavioral context by mentioning the fresh fetch from the provider and the absence of Kalendia calendar id, which is useful 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?

Two focused sentences front-load the core purpose and then add essential output/alternative guidance without unnecessary detail.

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 output schema is present and readOnlyHint is annotated, the description is complete for usage: it explains key fields, how to use them in get_agenda, and when to choose the sibling tool list_all_calendars.

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?

With one parameter (connection_id) and 0% schema coverage, the description adds some context via 'under one connection' but does not explain where the connection id comes from or validate any constraints beyond 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?

The description clearly states the tool lists live provider calendars under one connection, with specific output fields. It distinguishes from list_all_calendars by noting this is the provider view with no Kalendia calendar id.

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?

It explicitly instructs to use provider_calendar_id as calendar_id in get_agenda and directs users to list_all_calendars when they need the numeric Kalendia calendar id for sync rules and scheduling pages, making the alternative clear.

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