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 mentions safety guards for each source mode but does not disclose side effects (e.g., overwrites, rate limits) or behavior for duplicate uploads. The output schema exists but is not referenced.

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 efficiently structured with bullet points for source modes, covering key information in a few lines without unnecessary verbosity.

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 output schema exists, return values are covered. However, the description omits prerequisites (e.g., project existence), error conditions, and idempotency. With no annotations, some gaps remain for a well-rounded understanding.

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 description thoroughly explains the complex 'source' parameter (discriminated union) and the 'split' parameter. However, it ignores other parameters (workspace, batch_name, tag_names, dry_run) even though schema coverage is 0%.

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 'Upload a single image to a Roboflow project' and details three distinct source modes, distinguishing it from sibling tools like 'roboflow_upload_images_batch' (batch upload) and 'roboflow_delete_image' (delete).

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 explains the source modes and split parameter but does not provide explicit guidance on when to use this tool versus alternatives (e.g., batch upload). It lacks 'when to use' or 'when not to use' context.

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