list_calendar_events

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds valuable behavioral context: the 31-day maximum range and the ISO 8601 format requirement for the date strings, which are not encoded in the annotations or schema. This goes beyond the 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?

The description is a single, well-structured sentence that front-loads the core action ('List Outlook Web calendar events') and appends the key constraint. No wasted words; every word earns its place.

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 presence of a rich annotations block and an output schema, the description is mostly complete. It clearly states the range constraint and format. The only missing contextual piece is behavior around maxResults, but overall the tool is adequately specified for its low complexity.

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?

With 0% schema description coverage, the description must compensate for all three parameters. It only explains the date range concept ('ISO 8601 range') which covers startsAfter and endsBefore implicitly, but it completely ignores maxResults. The parameter names are self-explanatory to some degree, but the lack of any mention of maxResults leaves a significant gap.

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 uses a specific verb and resource: 'List Outlook Web calendar events', which clearly distinguishes this tool from sibling email tools like search_emails and get_email. The additional scope of 'ISO 8601 range of at most 31 days' further clarifies the tool's purpose.

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 use for retrieving calendar events within a bounded date range, which is distinct from sibling tools. There is no explicit exclusion or alternative guidance, but the context is clear enough for an agent to select this tool over email-focused siblings.

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