upload_picture

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

With no annotations, the description carries the full burden and does well: it discloses that url is downloaded by Meli, that file_path is sent as multipart, and what the response contains (picture id, source URL, size variations). It does not mention auth/permission requirements, file size limits, or rate limits, which are relevant for an upload endpoint.

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?

Three sentences, front-loaded with purpose, then the input constraint, then the create_item integration, then the return shape. Every sentence carries new information with no filler.

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?

No output schema exists, but the description explains the return value, and with only two fully documented parameters and no annotations there is nothing an agent needs to invoke this tool correctly that 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?

Schema coverage is 100%, so the baseline is 3, but the description adds the mutual-exclusivity rule ('exactly ONE of') that the schema does not encode via required/oneOf, plus clarifying that url is public and downloaded by Meli and file_path is a local multipart upload.

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?

States a specific verb and resource ('Upload a picture to the seller's Mercado Livre account') plus the concrete outcome ('get back a picture id'). It is clearly distinguishable from the sibling upload_video and from create_item, which it explicitly references.

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?

Gives explicit routing: use the returned id in create_item's pictures for local files, but for already-hosted public URLs you can pass the URL straight to create_item. It also states the input constraint ('exactly ONE of url or file_path'), so an agent knows both when to call it and when to skip it.

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