hs4.admin.events.delete

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states 'delete', which implies mutation, but does not explain side effects, reversibility, or confirmation requirements (despite the schema having confirm, dryRun, etc.). No mention of auditability or required change tickets.

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 a single sentence, which is concise but under-specified. It lacks an introductory summary or structured details. It is not verbose, but it could be more informative without becoming long.

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?

Given the tool has 12 parameters, no output schema, and no annotations, the description is too minimal. It does not cover return values, error conditions, or usage context. Sibling tools are diverse, but no guidance is provided on how this tool fits into workflows (e.g., using hs4.change.prepare first).

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 75%, so the baseline is 3. The description adds no information about parameters beyond what the schema already provides. It does not explain the meaning of key parameters like eventId, name, or group, which lack descriptions in the 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 clearly states the action ('Delete'), the resource ('event definition'), and the context ('through admin controls'). This distinguishes it from sibling tools like hs4.admin.events.create, hs4.admin.events.update, and non-admin event tools.

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 provides no guidance on when to use this tool versus alternatives (e.g., other event mutation tools or disabling events). It does not mention prerequisites, such as required admin privileges or that it should only be used for permanent removal versus temporary disablement.

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