Respond to Invitation

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

Annotations only declare the generic profile (not read-only, not idempotent, open-world, non-destructive). The description adds genuinely useful behavioral detail beyond that: the response is emailed to the organiser by default, and that external side effect is gated behind confirm=true. It stops short of noting reversibility or that a sent email cannot be recalled.

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 dense, front-loaded sentences that carry the action set, the proposed-time restriction, and the confirm gate with no filler 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 mutation tool with an output schema available, the description covers the essentials an agent needs to act correctly, especially the subtle confirm requirement for the default email path. Return values needn't be described since the output schema exists.

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 the schema already documents all 8 parameters including action enum, confirm, send_response, and the tentative/decline-only constraint on proposed times. The description largely restates these constraints rather than adding new semantics, so the baseline of 3 applies.

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 states a specific set of verbs (accept, tentatively accept, decline) against a specific resource (a meeting invitation), plus the optional proposed-time variation. This is clearly distinguishable in spirit from calendar_create_event/calendar_update_event, though no sibling is named to make the boundary explicit.

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?

Guidance is embedded and actionable: proposing a new time is only valid with tentative or decline, and confirm=true is required when the response is emailed (the default). It gives clear conditions for use but never explicitly contrasts with competing siblings like calendar_update_event.

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