delete_event

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

No annotations provided, so the description fully discloses behavior: soft-delete, immediate hiding, 7-day retention before permanent purge. This conveys the crucial mutation and data lifecycle aspects clearly.

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 efficient sentences, front-loaded with purpose and followed by key behavioral details. No wasted words.

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 simple 1-param tool with no output schema, the description covers behavior thoroughly: soft-delete, immediate effects, data retention, permanent purge. It misses only a mention of return value or error conditions, but overall is nearly complete.

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?

With 0% schema description coverage, the description adds no meaning to the single parameter event_id beyond what the schema provides (just a string type). The description could have explained that event_id identifies the event to delete, but it did not.

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 'Soft-delete an event,' using a specific verb and resource. It distinguishes from sibling tools like restore_event by explaining the soft-delete behavior and data retention policy.

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 (soft-delete), what immediately happens (event hidden, photos stop appearing), and that it can be restored within 7 days. It mentions restore_event as a recovery option, but does not explicitly discuss when not to use this tool vs alternatives like update_event.

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