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

Annotations already mark the tool as destructive (destructiveHint=true), and the description adds meaningful context beyond that: the operation is irreversible, and email template HTML referencing deleted URLs will show broken images. It also specifies permission requirements, which helps the agent anticipate errors.

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 compact and well-structured. It opens with the core action and irreversibility, then adds the URL-source guidance, the broken-image consequence, and finally the access requirements. Every sentence adds relevant information without padding.

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 destructive tool, the description covers the key operational context: how to obtain valid inputs, irreversibility, side effects, and required permissions. There is no output schema, but the description does not need to explain return values in depth for a delete operation; a small gap is the lack of any mention of success or failure response behavior.

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 100%, so the schema already documents the URLs array, minimum item count, and example. The description repeats the source guidance (src/destinationUrl) but does not add significant new parameter-level meaning beyond what the schema already provides.

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 uses a specific verb and resource: 'permanently delete one or more images from the Nevent media library.' It clearly distinguishes the operation from sibling tools by specifying the target resource and even tells the agent where to source valid URLs (nevent_list_images or nevent_upload_image).

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 gives clear prerequisites for use: URLs must come from nevent_list_images or nevent_upload_image, and FULL operation mode with ADMIN, SUPERADMIN, or OWNER role is required. It does not explicitly compare against alternative tools, but for a deletion operation the context and preconditions are well stated.

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