outlook_list_events

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

Annotations declare readOnlyHint=true, which is consistent. Description adds behavioral traits: expands recurring instances and mentions the concise parameter drops large fields (body, attendees, organizer, categories) for ~10x fewer tokens. No contradictions.

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?

Three concise sentences with no fluff. Front-loaded core purpose, then usage guidance, then parameter hint. Every sentence adds value.

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?

Describes key behavioral trait (recurring expansion) and concise mode, but lacks explanation of return values (no output schema) and other parameters. For a list tool with 6 parameters, marginally sufficient but not exhaustive.

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 description coverage is 0%, so description must compensate. It only explains the 'concise' parameter (its effect and token savings). Other parameters (days, after, before, count, cursor) are not elaborated, leaving meaning uncovered.

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 states 'List calendar events in a date range (expands recurring instances).' This clearly identifies the verb (list), resource (calendar events), and scope (date range, recurring expansion). It distinguishes from sibling tools like outlook_list_events_delta and outlook_rsvp.

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?

Explicitly says 'Use for one-shot queries; use outlook_list_events_delta for polling/recurring agents.' This provides clear when-to-use and when-not-to-use guidance with a named alternative.

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