calendar_list_events

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

With no annotations provided, the description carries the full burden. It reveals the REST endpoint and the read-only nature (GET), but does not disclose additional behavioral aspects such as pagination, rate limits, authentication requirements, or whether it returns all events or only basic info.

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 extremely concise with two sentences. The first sentence states the core purpose, and the second provides the REST endpoint detail. Every word is relevant with no filler.

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 that an output schema exists (context: Has output schema: true), the description need not detail return values. It adequately covers the primary purpose and input format. Minor gaps include lack of mention of event types (e.g., recurring events) or error handling, but overall it is sufficiently complete.

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 adds context for the start and end parameters by specifying ISO 8601 datetime format, which is not in the schema. However, the entity_id parameter is left unexplained, and with 0% schema coverage, the description only partially compensates. Overall, it adds moderate value beyond the schema.

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 action (list events), the resource (calendar entity), and the scope (between start and end). It distinguishes itself from sibling tools like calendar_create_event, calendar_delete_event, and calendar_list_calendars by specifying the date range filtering.

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 the tool is for listing events in a specific date range for a given calendar. However, it does not explicitly state when to use this tool over alternatives (e.g., search tools or calendar_list_calendars) and does not mention any exclusions or caveats.

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