upload_image

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

No annotations are provided, so the description carries full responsibility. It discloses the return of a public URL and the auto-deletion behavior via the 'expiration' parameter. However, it does not mention file size limits, supported formats, or error handling, which are important for a write 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 concise, with only two sentences and a clear bulleted parameter list. Every sentence serves a purpose, and the structure is easy to parse. There is no redundant information.

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?

The tool has an output schema (mentioned in context), so the description does not need to detail return values beyond mentioning the public URL. The description covers the main purpose, parameters, and a behavioral trait (expiration). Minor gaps include missing file size or format constraints, but overall it is sufficiently complete for an upload 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?

Schema coverage is 0%, meaning the description provides all parameter meaning. It explains 'file_path' as an absolute or relative path, 'name' as an optional image name, and 'expiration' with a numeric range (60-15552000) and its effect (auto-deletion). This adds significant value beyond the schema.

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?

Description clearly states 'Upload a single image file to ImgBB and return its public URL.' This provides a specific verb and resource, and the result is mentioned. It distinguishes from siblings 'list_images' and 'upload_all_images' by emphasizing 'single' and the service (ImgBB).

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 what the tool does but does not explicitly state when to use it versus siblings. While it implies use for single images, it does not mention alternatives like 'upload_all_images' for batch uploads or 'list_images' for viewing. Usage context is implied rather than explicit.

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