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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so safety is covered. The description adds genuine context beyond that: it discloses the limitation that only host-created events can be deleted, which is not derivable from the structured fields. It still says nothing about irreversibility or error behavior.

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 sentences, zero filler, and the constraining qualifier ("host-created") is front-loaded before the scope mechanics. Every clause carries information an agent needs.

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 two-parameter destructive tool with full schema coverage, full annotation coverage and no output schema, the description covers the action, the target restriction and the one non-obvious parameter's semantics. Nothing required to call it correctly 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 the baseline is 3, but the description goes beyond the terse schema text ("Delete scope for recurring events (default: 'single')") by explaining in plain language what each of 'single', 'future' and 'all' actually removes. That materially reduces the chance of a wrong scope choice.

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?

Specific verb + resource ("Delete a host-created event"), and the qualifier "host-created" narrows the target meaningfully against siblings like neuron_delete_calendar and neuron_delete_event_type. It does not, however, explicitly route the agent away from overlapping tools such as neuron_cancel_booking or neuron_mark_no_show.

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?

It gives conditional guidance ("For recurring events, use scope to control what gets deleted"), which implies when each scope applies, but there is no statement of when to use this tool versus cancel/skip alternatives, nor any prerequisite (e.g., auth, host ownership) spelled out.

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