Create Invitee No Show

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

Annotations already declare destructiveHint=true, non-idempotent and open-world, so the safety profile is covered. The description adds two genuinely non-annotated facts: that the operation changes Calendly state and that it requires the scheduled_events:write scope, plus the confirm=true requirement. It stops short of saying whether the change is reversible or what the response contains.

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 tight sentences, no filler, and the state-change warning is front-loaded before the scope requirement. Slightly redundant with the confirm parameter's own schema description, but nothing wasteful enough to penalize further.

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?

A destructive 5-parameter mutation with a nested payload object and no output schema needs more explanation than this. Scope, confirm, and state-change are covered, but the meaning of the no-show entity, the invitee identifier's role, and the payload-vs-body-flags alternative are all left to the schema.

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 80%, so the schema largely documents account, confirm, payload and payload_file on its own. The description's only parameter-related content (confirm=true) duplicates the schema wording, adding no new syntax or interaction detail. Baseline 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 verb and resource ("Create Invitee No Show") but essentially restates the name/title without explaining what marking a no-show means or how the resulting record relates to an invitee. It does not differentiate against close siblings like get_no_show or delete_no_show. Understandable but vague on actual effect.

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 and no routing to alternatives (get_no_show, delete_no_show are never mentioned). The only usage constraint given is the confirm=true gate, which is a precondition rather than situational guidance. An agent must infer context entirely.

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