Delete Invitee No Show

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the confirm=true requirement for the specific write and the required OAuth scope (scheduled_events:write). It stops short of describing irreversibility or side effects on related invitee/event data.

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?

Three short, front-loaded sentences with no filler, and the confirm and scope requirements are stated directly. Minor waste in the opening sentence, which duplicates the name/title, but overall efficient.

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 destructive mutation with no output schema, the description covers the confirm gate and required scope, which is the essential operational context. It leaves gaps an agent would care about: irreversibility, what happens to the related invitee/event records, and what (if anything) is returned. Adequate but not thorough.

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 67%: the schema already documents account and confirm, and the description's confirm=true restatement adds little beyond it. The required no_show_uuid parameter has no description in either the schema or the description, and the description does not explain what a no-show UUID refers to or where it comes from. Baseline 3 for mid coverage with no compensating detail.

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 first sentence, "Delete Invitee No Show," simply restates the tool name and title without adding scope, target, or distinguishing detail. "Changes Calendly state" is vague and does not clarify what is destroyed or how this differs from siblings like create_no_show, get_no_show, or delete_invitee_data.

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 when-to-use guidance, no exclusions, and no routing to alternatives despite having close siblings (get_no_show, create_no_show, delete_invitee_data). The only precondition given is the confirm=true gate, which is a mechanical requirement rather than usage guidance.

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