list_calendar_events

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

No annotations are provided, so the description carries the full burden. It states the basic operation and optional filters, but does not disclose what events are returned (e.g., default behavior with no filters, pagination, return format), permissions required, or any other behavioral traits. This is a significant gap for a tool with no output schema.

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 a single, front-loaded sentence that avoids redundancy. Every word contributes to explaining the purpose and key options, with no filler or repetition.

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?

The tool has five optional parameters and no output schema, yet the description only covers the core listing and filtering behavior. It omits return value details, pagination, default scope, and any usage prerequisites. For a tool with this complexity and no annotations, the description is underspecified.

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 has no parameter descriptions (0% coverage), so the description's mention of 'courses/groups/categories' and 'timestart/timeend range' adds meaning to all five parameters. It clarifies their purpose as filters, but does not explain how they combine or whether both timestart and timeend are needed together. These are reasonable basics but not comprehensive.

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 filtering dimensions (courses/groups/categories, timestart/timeend). This distinguishes it from sibling tools like create_calendar_event, update_event, and delete_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 implies when to use the tool (to list calendar events) but does not explicitly say when not to use it or compare to alternatives. It provides context about optional filters, which implies usage for retrieval, but no direct exclusions or alternatives are mentioned.

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