decline-calendar-event

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

The description discloses that the event remains in the calendar as declined after the action, and mentions optional body fields. Annotations indicate destructiveHint=true and readOnlyHint=false, which the description supports with mutation 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?

Description is concise with two paragraphs, but the structure could be more organized. It earns its place without 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?

Given the presence of nested parameters and no output schema, the description covers main action, optional proposal feature, and post-decline state. Missing are return value details and error scenarios.

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 75%, and the description adds meaning for proposedNewTime and body fields with examples. However, it omits includeHeaders and excludeResponse parameters. This compensates partially but not fully.

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 the tool declines a calendar event invitation, with a specific verb (decline) and resource (event in calendar). It is distinct from sibling tools like accept-calendar-event, cancel-calendar-event, etc.

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 explains when to use the proposedNewTime parameter and provides a tip with example body options. However, it does not explicitly differentiate from accept or cancel tools, nor state when not to use.

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