roboflow_delete_version

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

Without annotations, the description adds the word 'Destructive' and the confirm parameter requirement, which gives some behavioral context. However, it does not disclose permanence, side effects on dependencies, or any rate limits, which would be important for a destructive operation.

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 extremely concise with two short sentences, no filler, and front-loads the core purpose.

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?

Given the tool has 5 parameters, a destructive nature, and an output schema, the description is too minimal. It does not explain the parameters, return value, or provide sufficient context for safe use.

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 schema has 0% description coverage, so the description needed to explain all parameters. It only adds meaning for the 'confirm' parameter by stating it must be 'yes', while leaving 'project', 'version', 'workspace', and 'dry_run' unexplained.

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 dataset version', specifying the verb and resource, which distinguishes it from sibling tools that perform other operations like creating or listing versions.

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 mentions that a confirm='yes' is required, implying usage conditions, but it does not explicitly state when to use this tool versus alternatives like archiving or when deletion is appropriate.

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