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

Beyond the destructive/idempotent annotations, it discloses consequences the annotations cannot: paid tickets are refunded, guests are NOT messaged (with a reminder to tell them), drafts are archived rather than canceled, canceled events remain in the list, and invalid targets return a plain message. This is exactly the side-effect detail an agent needs before a destructive call.

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?

The trigger condition and core behavior are front-loaded in the first two sentences, and every clause carries actionable information. It is dense and the final sentence bundles two alternatives (update-event and publish) in one line, which is slightly crowded but still parseable.

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 full picture: what happens to tickets, what happens to guests, what happens to drafts, what happens to the list entry, what a failed call looks like, and the confirm-before-commit protocol. Nothing material is missing.

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 100%, so baseline is 3; the description adds real value by prescribing the dry_run:true-first protocol and by tying event_id to 'the member's own event' found via connections_events_list. The person/project parameters are left to the schema, which is acceptable given full coverage.

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?

States a specific verb and resource ('cancel... one of their own hosted events by id') and immediately clarifies the dual behavior (cancel published vs archive draft). It explicitly distinguishes itself from connections_event_delete and connections_event_publish, so an agent can pick it apart from siblings without opening schemas.

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?

Gives a concrete trigger ('cancel my meetup'), a mandatory two-step workflow (dry_run:true first, confirm, then real call), and explicit alternatives for adjacent intents (delete to remove, publish to put a draft live, update-event to edit a staying event). Exclusions are named: not-own, already-canceled, or archived events are rejected.

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