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

Annotations already cover destructiveness and non-idempotency, but the description adds useful behavior: Partiful notifies guests and the cancellation waits for owner approval. It omits whether the call blocks until approval and whether the cancellation is reversible, so it stops short of full disclosure.

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 sentences, with the core action stated first and the two relevant behavioral traits following. No filler.

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, approval-gated mutation with full schema coverage and no output schema, the description supplies the key workflow context. It could be more complete by explaining whether the call blocks until approval or what happens on rejection.

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 event_id, message, and notify_guests are already documented. The description does not add syntax or constraints beyond the schema; the statement that Partiful notifies guests is also slightly misleading because notify_guests can be set to false.

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?

It states a specific verb and resource ('Cancel an event') and is clearly a mutation. However, it does not distinguish this from the sibling delete_event, leaving the agent to infer the difference between canceling and deleting an event.

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 mention that it 'waits for the owner's approval' implies a specific workflow, but the description never states when to choose cancel_event over delete_event or what happens if approval is denied. Usage is implied rather than explicit.

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