list_calendar_events

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

With no annotations, the description carries the full burden. It clarifies the time format (Unix seconds) and gives an example range, but does not disclose pagination behavior, sorting, or whether all events are returned when no time range is specified. The read-only nature is implied but not explicitly stated.

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 sentences long, front-loaded with purpose, and every sentence adds essential information. The typical usage example is concise and highly informative, with no wasted words.

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 list tool with 6 parameters and no output schema, the description covers the core workflow and time range usage, which is sufficient for most cases. However, it does not elaborate on pagination behavior or response structure, leaving some gaps for comprehensive understanding.

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 already covers all parameter descriptions, so the baseline is 3. The description adds value by explaining how calendar_id is discovered (via list_calendars) and by providing a concrete example time range ([now, now+7d]), which helps agents construct valid parameter values.

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 ('List') and resource ('events in a calendar') and clearly states the optional time range. It also provides a typical usage flow involving list_calendars, distinguishing it from singular event retrieval tools like get_calendar_event.

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 explicit workflow context: first list_calendars to obtain calendar_id, then use this tool with a time range. It does not explicitly state when not to use alternatives like get_calendar_event, but the typical usage strongly implies the appropriate context.

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