delete_published_image

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 key side effect (auto-cleaning the parent PublishedAsset when the last image is removed). However, it omits other important behavioral information such as irreversibility, permissions, or whether the delete is hard or soft, making it only partially transparent.

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 only two sentences long, with no redundant or filler content. The key action and side effect are stated efficiently and in a clear order.

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 one-parameter delete tool with no output schema, the description provides the essential action and an important cascade effect. It is sufficiently complete, though it could mention irreversibility or other consequences, but those are largely implied by the term 'delete'.

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?

The input schema already covers the sole parameter (id) with 100% description coverage, so the baseline is 3. The description adds no additional meaning about the id beyond what the schema provides; it only implies that the id refers to a PublishedImage row.

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 a single PublishedImage row') with a specific verb and resource. It also distinguishes this from sibling delete tools by naming the exact entity type, and the auto-clean behavior adds further clarity.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., delete_asset) or when not to use it. The description is purely functional and gives no contextual usage cues.

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