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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description adds real value beyond that by disclosing the downstream consequence (pages will render a broken image) and the auth requirement (API key). It stops short of saying whether the image must be in a particular state or what is returned on success.

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?

Four short sentences, with the destructive nature and side effect front-loaded and the confirmation warning before the auth note. Nothing is padded or repeated from the annotations.

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 single-parameter destructive tool with no output schema, the description covers the essentials: irreversibility, blast radius, user confirmation, and auth. The one meaningful gap is where the image_id comes from, which matters for an agent that must first discover an image.

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 0%, so the description must carry parameter meaning, yet it never explains that image_id is the UUID of the image nor how to obtain one (e.g., from list_images). "Kept image" is the only hint about which images are eligible, and it is left undefined.

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 and resource ("Permanently delete a kept image") and scopes it to images rather than pages, which distinguishes it from the sibling delete_page. The qualifier "kept" is slightly ambiguous without knowing the image lifecycle, but the intent is unmistakable.

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?

Explicitly tells the agent to confirm with the user first and flags that the operation is irreversible, which is exactly the gating guidance needed for a destructive tool. It doesn't name delete_page or discuss alternatives, but the resource split is obvious from the name.

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