outlook_list_events

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

No annotations are provided, so the description carries full burden. It only says 'list', implying a read operation, but does not disclose whether it returns all events, pagination behavior, or performance implications. Lacks necessary context for safe usage.

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 extremely short (one sentence), but it achieves its basic purpose. Could be more informative without being verbose, e.g., adding scope or output format. Not too long, but too sparse.

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 no parameters and no output schema, the description is minimal but leaves ambiguity about which calendar is used, date range, or ordering. The existence of a similar sibling tool further reduces completeness. More detail is warranted.

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?

There are 0 parameters, and schema coverage is 100% (vacuously). Baseline is 3 per rules for high coverage. The description adds no parameter-specific info, but none is needed. However, it could hint at implicit filtering (e.g., 'lists all upcoming events') which is missing.

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 Outlook calendar events', which is a clear verb+resource. However, there is a sibling tool 'list_calendar_events' with nearly identical purpose, and the description does not differentiate between them or specify any scope (e.g., date range, calendar identity).

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 on when to use this tool versus alternatives like 'list_calendar_events' or 'outlook_list_emails'. No when-not or prerequisites mentioned.

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