google-calendar_list_calendars

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

No annotations exist, so the description carries full burden for behavioral disclosure. It only states 'returns calendars' but fails to mention whether pagination is automatically handled, if there are rate limits, or if hidden/deleted entries affect results. The schema parameters hint at behaviors, but the description adds no transparency beyond that.

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, concise sentence that is easy to read. It is appropriately front-loaded but could benefit from additional structure, such as a quick note on pagination or the default behavior of parameters.

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 no output schema, the description should mention what the returned data contains (e.g., list of calendar objects). It does not. With 5 parameters, it lacks guidance on how to combine filters (e.g., minAccessRole with showHidden). The description is incomplete for a user unfamiliar with Google Calendar API.

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 coverage is 100%, so the description does not need to compensate. However, it adds no additional meaning beyond the schema descriptions, which are already clear. Baseline of 3 is appropriate.

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 it returns calendars from the user's calendar list. The verb 'returns' and resource 'calendars on the user's calendar list' are specific and distinguish it from sibling tools that create, delete, or modify calendars or events.

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 gives no explicit guidance on when to use this tool versus alternatives. However, the context of sibling tools (e.g., list_events) implies this is for listing calendars, not events. No when-not or alternative recommendations are provided.

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