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

With no annotations provided, the description carries the behavioral disclosure burden. 'Read' clearly signals a non-mutating operation, and it adds useful return-content context: a full event including guest addresses and their acceptance status. It does not discuss error behavior or authorization, but for a simple read tool the core behavior is transparent.

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 sentence that front-loads the action and scope, then adds the valuable guest-list detail. There is no filler, repetition of the title, or irrelevant 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?

For a two-parameter read tool, the description is largely sufficient: it states what is returned, signals read-only behavior, and relies on the schema for mailbox documentation. The main gap is that eventId provenance is not explained, but given the tool's simplicity this is a minor omission.

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 only 50%. The mailbox parameter is documented in the schema, but eventId is only typed as a string with no explanation. The description does not explain what eventId should be, how to obtain it, or that it likely comes from a previous list or search call, so it fails to compensate for the missing schema documentation.

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 opens with 'Read one event in full', identifying a specific verb and resource, and adds the distinctive detail that the guest list, each guest's address, and acceptance status are returned. This clearly separates it from list/search siblings that deal with multiple events or summaries.

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 phrase 'one event in full' implies it should be used when a single known event's complete details are needed, rather than for listing or searching. However, the description does not explicitly name alternatives like list_outlook_calendar_events or search_outlook_calendar_events, nor does it state when not to use this tool.

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