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 behavioral burden. It discloses the write destination and the key return value, but it omits important mutation details such as overwrite behavior, supported formats, size limits, and permission or authentication requirements.

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 a single front-loaded sentence with the action, destination, and return value stated efficiently. There is no filler or repetition.

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 that an output schema exists, return-value details are mostly covered elsewhere, and the description adequately explains the basic call flow. However, with no annotations and 0% schema description coverage, the missing explanation of the optional `name` parameter and upload constraints leaves meaningful gaps.

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 explain both parameters. It implies that `path` refers to a local image, but it does not clarify path format or location, and it does not explain the optional `name` parameter at all.

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 states a specific verb and resource (upload a local image) and names the destination (server's input folder). It also connects the output directly to the sibling tool run_workflow, so the agent can distinguish this preparatory upload step from workflow execution.

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?

It gives clear context for when to use the tool: before run_workflow when an image must be uploaded and its returned name supplied. It does not explicitly cover exclusions or alternatives, such as remote URLs or directly passing existing server-side images.

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