ews_cancel_meeting_preview

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

No annotations are provided, so the description carries the full burden. It discloses that the tool does not delete, move, or send cancellations, indicating it is a read-only preview. However, it does not mention any other behavioral traits like whether it modifies state, requires specific permissions, or has rate limits. For a preview tool, the disclosure is adequate but not exhaustive.

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 is front-loaded and contains no redundant information. Every word serves a purpose.

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 annotations and no output schema, the description is fairly complete for a preview tool. However, it does not describe the return value or what the preview actually shows (e.g., list of affected attendees). This is a gap that could be filled.

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 clear descriptions. The description adds value by emphasizing the use of 'exact' id and changekey, and implicitly clarifies that the send_meeting_cancellations parameter is ignored (since it states 'does not send cancellations'). This provides semantic context beyond the schema.

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 tool's purpose: 'Preview cancellation of an existing meeting using exact id and changekey.' It also explicitly states what it does not do ('does not delete, move, or send cancellations'), distinguishing it from siblings like ews_cancel_meeting_confirmed that actually send cancellations.

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 that this tool is for previewing before actual cancellation, with the sibling ews_cancel_meeting_confirmed for the actual action. However, it does not explicitly state prerequisites (e.g., need to have the id/changekey from a previous fetch) or scenarios when to choose this over other tools.

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