calendar_list_events

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

No annotations are provided, so the description must disclose behavioral traits. It only states the tool lists events and uses a REST GET call, but fails to mention important aspects like whether events are sorted, pagination behavior, or any side effects. The output schema may cover return values, but the description itself offers minimal transparency.

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 very concise with two sentences: the first states the core functionality, and the second provides the REST endpoint. There is no redundant information, and the important details are front-loaded.

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?

Given the tool's simplicity and the existence of an output schema (context signal shows true), the description is minimally adequate. However, it lacks usage guidelines and behavioral transparency, which would be needed for full completeness. It leaves gaps about time range inclusivity and sorting.

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 0%, so the description must add meaning. It specifies that 'start' and 'end' are ISO 8601 datetimes, which adds format context, but 'entity_id' is only identified as a calendar entity without further detail. This partial compensation earns a 3.

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 the tool lists events for a calendar entity within a given time range. It uses a specific verb ('List') and resource ('events'), and distinguishes from sibling tools like calendar_create_event (creates) and calendar_list_calendars (lists 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 implies usage for retrieving events in a date range, but provides no explicit guidance on when to use this tool versus alternatives (e.g., calendar_list_calendars for finding calendars, or calendar_delete_event for deleting). No exclusions or context are given.

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