upload_image

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

No annotations are provided, so the description must carry the full burden. It discloses file size and format constraints but does not mention success/failure responses, authentication requirements, or any side effects (e.g., overwriting existing files).

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 sentences, no fluff, and front-loads the essential information immediately.

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 there is no output schema, the description should explain what the tool returns upon success (e.g., an image ID or URL). It also omits prerequisites like authentication. The file constraints are covered, but the output behavior is missing.

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 already describes both parameters (100% coverage). The description adds value by reiterating the absolute path requirement and adding file size/format constraints not in the schema. However, it does not elaborate on the 'media_category' parameter's purpose or options beyond the default.

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 ('upload'), the resource ('image file'), and includes constraints (max 5MB, allowed formats JPEG/PNG/WebP/GIF). It implicitly distinguishes from sibling 'upload_video' by specifying 'image file'.

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 tells the user to provide an absolute file path and lists file size/format restrictions, but does not explicitly state when not to use this tool (e.g., for non-image files) or mention alternatives like 'upload_video'.

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