roboflow_delete_image

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

No annotations are provided, so the description must cover behavioral traits. It mentions destructiveness and required confirm/mode, but fails to disclose other important behaviors like idempotency, error handling, or effects on related data.

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, with one sentence and a conditional clause. It front-loads the purpose. However, it could be slightly more structured to highlight the requirements.

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?

While an output schema exists and the description need not explain returns, the tool has 5 parameters with only 2 required. The description omits guidance on optional parameters like dry_run, and does not provide enough context for a destructive action.

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 should clarify parameters. It only implicitly addresses 'confirm' by stating it must equal 'yes', and mentions mode but not as a parameter. Other parameters like project, image_id, workspace, and dry_run are not explained.

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, with specific verb and resource. It lacks explicit differentiation from sibling delete tools like roboflow_delete_version, but the tool name is self-explanatory.

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 indicates when to use (for deleting images) and includes prerequisites (confirm, mode), but does not provide guidance on when not to use this tool or alternatives.

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