roboflow_upload_image

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

No annotations are provided, so the description carries the full burden. It identifies the action as an upload but does not disclose side effects, authentication needs, rate limits, idempotency, or what happens on duplicate images. For a mutation tool, this is a significant transparency gap.

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?

Two short sentences, front-loaded with the action. No filler or repetition. The split instruction is relevant and earns its place. Very efficient.

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?

With 5 parameters, no annotations, and no output schema, the description is minimally adequate but leaves gaps. It explains the core purpose and split, but omits behavioral details (auth, side effects) and does not mention what happens after upload. The schema covers parameter details, so this is not a severe gap, but it is not complete for a mutation tool.

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 covers all parameters with descriptions (100% coverage), so the baseline is 3. The description only repeats the split parameter without adding deeper meaning (e.g., accepted image formats or behavior with the 'tag' parameter), so it doesn't elevate above baseline.

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 uses a specific verb ('Upload') and resource ('image to a Roboflow project dataset'), clearly distinguishing it from sibling tools like 'roboflow_inference_run' or 'roboflow_project_list'. It also highlights the key split parameter, making the tool's purpose unambiguous.

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 context is clear: this tool is for uploading images into a dataset split, as opposed to inference, listing, or workflow tools. It does not explicitly name alternatives or exclude non-training splits, but the context is sufficient for an agent to know when to select it.

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