delete_image

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

No annotations are provided, so the description carries full responsibility for behavioral transparency. It only states that the tool deletes an image, but lacks details on side effects (e.g., irreversible deletion), required permissions, or return value. The output schema may provide some info, but it is not shown. The description is insufficient for understanding the full impact of using this tool.

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 very concise—three sentences with no redundancy. It front-loads the purpose, gives a usage hint, and then lists parameters. Every sentence earns its place.

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?

The tool is simple with two required parameters. The description covers the core use case but lacks information on return values (though output schema may exist) and behavioral implications. For a deletion tool, more context about irreversibility would improve completeness.

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 compensate. It adds only that image_index is 0-based, which is minimal. file_path is not explained beyond its name. This adds little value beyond the schema titles.

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 tool deletes an image at a specified index in a document. It uses the verb 'delete' and specifies the resource as an image by index. This effectively distinguishes it from sibling tools like add_image, replace_image, etc.

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 provides a useful hint to use get_images_info to find image indices. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it (e.g., no prerequisites or conditions). The guidance is implicit but not comprehensive.

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