list_calendar_events

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

The description indicates a read-only operation (listing events) but does not disclose details like pagination, ordering, or whether historical events are included if the 'to' date is in the past. Despite the absence of annotations, the basic behavior is adequately implied.

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, consisting of a single line. It is front-loaded with the tool's name and purpose, but could be slightly more structured by separating the title from the explanation.

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 lack of output schema, the description covers the basic scenario but omits details like pagination, event ordering, or whether the 'upcoming' qualifier restricts results to future dates. It is adequate for a simple list tool but not fully 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 input schema already provides clear descriptions for all three parameters (date format, status values). The description adds minimal extra meaning beyond stating the overall purpose of listing events in a date range.

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 verb 'List' and the resource 'Calendar Events', and specifies the date range scope. However, it does not differentiate from the sibling tool 'list_calendar_events_ops', which may have overlapping functionality.

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?

No guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. The description only states what it does, not the context for use.

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