outlook_rsvp

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is carried structurally. The description adds nothing beyond that: it doesn't say that a response is sent to the organizer, that "decline" may remove the event from the calendar, or whether an RSVP can be changed afterward — meaningful gaps given destructiveHint=true.

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, no filler, with the action and its allowed values front-loaded and the disambiguation trailing. Every clause earns its place.

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 3-parameter mutation with no output schema and no documented return behavior, the description covers the response values but says nothing about where event_id is obtained (siblings outlook_list_events / outlook_get_event exist) or what message does. Adequate to avoid a wrong tool choice, but not complete for correct invocation.

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 0% and no enums are defined, so the description's enumeration of accept/decline/tentative is genuinely load-bearing and prevents an invalid call. However, `event_id` (where does it come from?) and the optional `message` (a note to the organizer?) are left entirely undefined, so it only half compensates for the coverage gap.

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 gives a specific verb+resource ("RSVP to a calendar meeting invite") and immediately constrains the operation with the three legal `response` values. It also names the sibling it is not (outlook_reply) for a regular email message, so an agent can route without opening either schema.

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?

It states the positive case ("Use this for meeting invites") and the alternative explicitly ("use outlook_reply to reply to a regular email message"), which is exactly the confusion an agent would face given how many mail-reply siblings exist.

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