List My Calendars

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

The description discloses that it requires delegated Calendars.Read and operates on the signed-in user's data, which is useful context. However, it does not explain default behavior for the optional 'top' parameter, ordering, or what happens if no calendars exist, so it only partially covers behavioral traits.

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 brief and front-loaded with the primary action, followed by the permission requirement and multilingual hints. Every sentence serves a purpose, and it avoids redundancy.

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 covers the purpose and permission clearly, but lacks details on default behavior and return format, especially since there is no output schema. The optional 'top' parameter's default value is not explained, leaving some ambiguity for a simple tool.

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 schema fully documents the single 'top' parameter with description, min, max, so schema coverage is 100%. The description adds no additional meaning about the parameter, so 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 explicitly states 'List calendars for the signed-in user' with a clear verb and resource, and the title reinforces it. This clearly distinguishes it from sibling tools like calendar_list_events that handle events rather than calendars.

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 provides clear context: listing the signed-in user's calendars, with a permission requirement. It does not explicitly mention alternatives or when not to use it, but the scope is unambiguous, earning a 4 rather than a 3.

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