etsy_listing_image_upload

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

The description indicates an upload operation but does not disclose behavioral details such as whether overwriting existing images is possible (though an 'overwrite' parameter exists), authentication requirements, or any rate limits. Since no annotations are provided, the description carries the full burden but only offers minimal insight.

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 very short at one sentence, which is concise, but it contains a misleading statement about base64 support. Being brief is good, but not at the expense of accuracy.

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 the lack of annotations, output schema, and only 57% parameter coverage, the description is insufficient. It fails to explain required parameters like shop_id and listing_id, or the implications of the 'overwrite' parameter. A mutation tool like this requires more context for correct usage.

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 description coverage is 57%, with missing descriptions for 'shop_id', 'listing_id', and 'is_watermarked'. The description mentions uploading via base64, but the input schema does not include a base64 parameter, which is misleading. This contradicts the schema and reduces clarity.

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 verb 'upload' and resource 'image to a listing', and specifies methods via URL or base64. It mentions rank 1 as primary, which adds context. However, it does not explicitly distinguish from the sibling tool 'etsy_listing_image_upload_url', which likely focuses on URL uploads.

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?

No guidance is provided on when to use this tool versus alternatives like 'etsy_listing_image_upload_url' or other image manipulation tools. The description does not specify use cases or exclusions.

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