modx_virtualpage_delete_event

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

With no annotations, the description carries the full burden, and it does disclose a meaningful side effect: deleting the event also removes its routes. However, it omits permissions required, reversibility, and what happens if both id and name are supplied or neither is.

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?

A single front-loaded sentence with no wasted words; the cascade side effect is parenthetically attached. Efficient, though the parenthetical 'per the VP schema' is slightly opaque.

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 mutation tool with no annotations, no output schema, and 0% parameter coverage, the description covers the core action and the cascade effect but leaves identifier precedence, required-input behavior, and permission requirements unaddressed.

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 0%, so the description must compensate. It adds that either id or name can identify the event, which is useful, but does not state precedence when both are given, whether one is required, or the expected formats.

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?

States a specific verb (Delete) and resource (VirtualPage event) plus the identifier options, which clearly distinguishes it from sibling delete tools like modx_virtualpage_delete_route or modx_virtualpage_delete_handler. It stops short of explicitly naming those siblings, so a 4 rather than 5.

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 phrase 'by id or name' hints at two lookup paths but gives no guidance on when to prefer one, no prerequisites, and no exclusions relative to the route/handler delete siblings. An agent must infer usage entirely.

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