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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds that it deletes a single event, which clarifies the target, but does not disclose any cascading effects, permission requirements, or irreversibility beyond what the annotation implies. Minimal added value over annotations.

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 description is short but contains redundancy: 'Delete event.' duplicates the title, and the trailing '| context: id' is cryptic and unexplained. The useful part is the second sentence, but the first sentence and the suffix do not earn their place, making the structure imperfect.

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 single-parameter delete tool, the description covers the core action and target. However, it does not mention return behavior, error cases (e.g., non-existent id), or any cascading effects. Given the low complexity, it is adequate but leaves some operational details unspecified.

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%: the 'id' parameter already has a description ('Event id returned by cms_list_events'). The tool description merely repeats 'by event id' without adding new semantics like format, constraints, or relationships. No extra meaning beyond schema.

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 specific verb (delete) and resource (CMS agenda event) with a clear scope (by event id). It distinguishes from sibling tools like cms_delete_event_paragraph by naming 'event' rather than a paragraph, making the target unambiguous.

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 implies usage when you want to delete an event by its id, but it does not explicitly state when to use this tool versus alternatives like cms_delete_event_paragraph or other delete tools. No exclusions or alternate routing is given; usage is inferred from the resource type rather than stated.

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