List My Calendar Events

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

No annotations are provided, so the description carries the burden. It adds useful context by mentioning 'Requires delegated Calendars.Read' and clarifies scope to 'the signed-in user.' However, it doesn't disclose response format, sorting, pagination, or how 'upcoming' is determined (beyond what schema params imply).

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 concise and front-loaded with the main action. It includes usage, permission, and multilingual hints in a compact format. The Chinese intent list adds some length but is useful for multilingual contexts and doesn't detract significantly.

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 tool with two well-documented parameters and no output schema, the description covers key aspects: scope, usage, permissions, and intent. It is not missing critical information for an agent to invoke it correctly.

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%, and both parameters (top, daysAhead) have clear descriptions. The tool description does not add additional meaning beyond what the schema already provides, so baseline 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 'List upcoming calendar events for the signed-in user' with a specific verb and resource. It distinguishes itself from sibling tools like calendar_list_calendars (list calendars) and calendar_get_event (single event) by focusing on upcoming events for the signed-in user.

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?

Explicit guidance is provided: 'Use for today, this week, or upcoming meeting queries.' This gives clear context for when to invoke the tool. It doesn't explicitly name alternatives but the usage context is sufficient for an agent to select it.

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