Upload a photo for an item

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

No annotations are present, so the description carries the burden. It adds useful detail about accepted formats, size limit, and the input modes. However, it does not disclose whether the upload overwrites an existing photo, what happens after success, or error conditions—leaving some behavioral ambiguity.

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 sentences, no filler, and front-loaded with the main action. Every sentence adds meaningful information—format, size, input modes, and the set-as-photo outcome.

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 description covers the core requirements for correct invocation: file types, max size, and the two input modes. It does not mention overwrite behavior or return values, which are gaps, but the tool is relatively simple and the given info likely suffices for most calls.

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 explains the critical either/or relationship between filePath and imageBase64, defines imageBase64 as 'raw base64-encoded bytes', and ties mimeType to the image type. This goes well beyond the input schema, which merely lists the properties without any description (0% schema coverage).

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 ('Uploads a local image file'), the target resource ('sets it as the item's photo'), and constraints ('JPEG/PNG/WebP, 5MB max'). It distinguishes from sibling set_item_image_url by emphasizing local file upload rather than URL.

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 implies usage when a local image file needs to be set as an item photo, but it does not explicitly compare with alternatives like set_item_image_url. It provides input-mode guidance (filePath vs imageBase64) but no when-to-use vs alternatives guidance.

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