Save an uploaded image to the media library

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

Adds genuinely useful context the annotations do not carry: the 100 requests / 10 seconds per shop rate limit with a docs link. However, with destructiveHint=true and idempotentHint=false, the description never explains what the operation destroys, whether repeats create duplicates, or why the 'confirm' flag exists – gaps that matter for a mutation.

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 tight sentences with no filler. The ordering places the rate-limit note ahead of the actual purpose, which is slightly backwards for front-loading, but the total length is well controlled.

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?

For a destructive, non-idempotent mutation with a nested payload object, no output schema, and no required-parameter signaling, the description omits too much: what gets destroyed, return behavior, and how the account/confirm semantics affect the call. The rate-limit note is the only extra context supplied.

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 only 57% and the description explains none of the 7 parameters. It notes an image was uploaded but does not map fileUrl, width, height, account, confirm, or the payload/payload_file body alternatives, leaving the agent without guidance on a schema where no parameters are even marked required.

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: 'Persists an uploaded image in the media library', and adds the workflow precondition (client already PUT to the signed URL). This differentiates it from siblings like request_media_upload_url and list_media_images, though it never names them explicitly.

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 phrase 'after the client has PUT it to the signed URL' implies when to call it (second step of the upload flow), but no alternative is named and no explicit when-not condition is given. Usage is inferable rather than stated.

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