ews_create_meeting_confirmed

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

No annotations provided, so description carries full burden. It states the tool sends invitations (destructive) and requires confirm=true and matching confirmation_id. It doesn't mention side effects like email notifications or idempotency, but the core behavior is disclosed clearly.

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?

Two sentences: first states purpose, second gives usage condition. No redundant information. Every word 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?

Given 10 parameters, 6 required, and no output schema, the description covers purpose, prerequisite (preview), and required flags. It does not describe return value or error cases, but for a create tool with sibling preview, this is adequate.

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 60% and already documents most parameters. The description adds context that confirmation_id must match the one from ews_create_meeting_preview and that confirm must be true. This adds semantic meaning 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?

Description clearly states 'Create a meeting and send invitations', providing a specific verb and resource. It distinguishes from sibling tools like ews_create_meeting_preview (preview step) and ews_update_meeting_confirmed (update vs create).

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 states 'Only call after the user explicitly confirms the exact attendees, time, subject, body, and location' and specifies required parameters confirm and confirmation_id. This gives clear when-to-use guidance and implies when not to use (before user confirmation).

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