m365_calendar_create

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

Annotations already indicate readOnly=false, so the agent knows this is a write operation. The description adds the behavioral detail of optional Teams meeting creation, but it does not disclose other important behaviors such as whether attendees receive invitations, required permissions, or side effects of openWorldHint=true. This is adequate but not rich context.

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 concise sentence with no redundant information. Every word earns its place, and it front-loads the core purpose. Ideal for a minimal description, though it sacrifices completeness.

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?

With 7 parameters, no output schema, and a mutation operation, the description is far too short. It does not mention return values (e.g., created event ID), what happens when isOnline is false, or any prerequisites. The tool's complexity demands more context than offered.

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 all 7 parameters having descriptions. The description does not add any parameter semantics beyond the schema; the mention of 'optional Teams meeting' simply reinforces isOnline, which is already described as 'Create as Teams meeting'. Baseline 3 is appropriate.

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 'Create a calendar event (with optional Teams meeting)' uses a specific verb and resource, clearly distinguishing it from sibling tools like m365_calendar_list, m365_calendar_update, and m365_calendar_delete. The optional Teams meeting feature adds a distinguishing detail that separates it from other calendar tools.

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 is provided on when to use this tool versus alternatives such as m365_calendar_update or m365_calendar_list. The description does not mention contexts like 'use for new events' or describe any exclusions, leaving the agent without explicit selection criteria.

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