Crear evento de calendario

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

Annotations indicate readOnlyHint=false, so the agent knows it's a write operation. The description adds the behavioral trait that passing attendees sends meeting invitations, which is beyond the schema and annotations, providing useful side-effect context without contradiction.

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 concise sentences, front-loaded with the primary purpose and a behavioral condition. No unnecessary words or repetition.

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 create tool with 6 parameters and no output schema, the description provides essential behavior (create event, optionally send invites) and distinguishes it among 18 siblings. It doesn't describe return values, but the schema covers parameter details adequately.

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 100%, so baseline is 3. The description explicitly mentions the attendees condition, reinforcing the schema's note, but does not add new parameter-level semantics for subject/start/end beyond what the schema already provides.

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 'Crea un evento en el calendario' (Creates an event in the calendar), specifying the action and resource. It also mentions 'CreateItem CalendarItem' which anchors the EWS operation, distinguishing it from siblings like ews_update_event, ews_delete_event, and ews_accept_event.

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 the tool is for creating calendar events, which differentiates it from update/delete/accept/decline siblings. However, it does not explicitly state when not to use it or point to alternative tools; the condition about attendees is a behavioral note rather than an alternative guide.

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