List calendar events

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds behavioral details: the date range is inclusive and a search query can filter events. It also provides an API documentation link. No contradiction with annotations.

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?

One concise sentence immediately states the verb and scope, followed by a useful documentation link. No wasted words or redundant repetition of schema information.

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 simple read-only nature, full schema coverage, and rich annotations, the description is sufficient. It clearly conveys the core behavior, and the return value (a list of events) is implied by the tool name and description. The API link provides additional detail if needed.

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 coverage is 100% with descriptive parameter documentation, so the description does not need to add much. It mentions 'search query' and 'inclusive date range', which align with the query and date parameters, but these are already in the schema. Baseline 3 is appropriate.

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'), the resource ('kalender.digital events'), and the scope ('within an inclusive date range, optionally filtered by a search query'). This distinguishes it from siblings like get_event (single event) and mutation tools.

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?

It provides clear context for when to use the tool (listing events in a date range with optional filtering), but does not explicitly mention alternatives or when-not-to-use, such as using get_event for a single event. The context is unambiguous, so this is above baseline.

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