Get Calendars

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds 'Scopes: calendars.readonly' and the GET endpoint, which provides some authentication context. Still, it does not disclose response shape or pagination behavior, though these are less critical given 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 description is short and efficient, containing the operation, endpoint, and scope. The only minor flaw is the redundant repetition of the tool title 'Get Calendars' at the start, which wastes a few words without adding information.

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 simple list operation with strong annotations and a fully documented schema, the description is minimally adequate. It does not explain how to choose between related calendar endpoints or describe the return format, but the core purpose and parameters are clear enough.

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 100%, so all parameters are documented in the schema. The description adds no meaning beyond 'location', but because the schema carries the full parameter burden, a baseline score 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 states a specific action and resource: 'Get all calendars in a location.' This clearly distinguishes it from siblings like calendars_get_calendar (singular) and calendars_get_calendar_events. Including the endpoint and scopes reinforces the exact operation.

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 context is understandable: use this to list all calendars for a location. However, it does not explicitly say when to prefer this over related calendar endpoints such as calendars_get_calendar or calendars_get_groups, and no alternatives or exclusions are mentioned.

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