List calendars available in a selected Google account. Use pagination to browse up to 100 calendars per page and continue with a cursor for additional results.
Discover calendars accessible to one explicitly selected account. Returns at most 100 per page with query-bound continuation.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | ||
| pageSize | No | ||
| accountId | Yes |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnly and destructive annotations already cover side effects, and the description adds transparency about pagination limits and query-bound continuation. It does not mention authentication or possible errors, but the behavior is consistent with 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 two concise sentences with no redundant or promotional language. It front-loads the core purpose and then gives a necessary pagination 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?
The description explains the scope and pagination but does not describe the returned calendar fields or any preconditions such as selecting the account via accounts_list. Since there is no output schema, a bit more detail about the response shape would improve completeness.
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 description gives partial meaning to parameters: 'one explicitly selected account' maps to accountId, 'query-bound continuation' maps to cursor, and 'at most 100 per page' maps to pageSize. It does not fully compensate for the 0% schema coverage, but the parameter names are self-explanatory and supported by these hints.
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 uses a specific verb ('Discover') and a clear resource ('calendars accessible to one explicitly selected account'), distinguishing it from event/instance listing tools. It also communicates the account-scoped nature of the 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 description clearly indicates when to use the tool: to discover calendars for a selected account. It does not explicitly name alternatives or state when not to use it, but the account-scoped purpose provides strong contextual guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.