etsy_listing_video_upload

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

Since no annotations are provided, the description carries full burden for behavioral disclosure. It only states the action without any details about side effects, required permissions, file format constraints, or whether it replaces an existing video. This is insufficient for an agent to understand the tool's behavior.

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 concise (one sentence) and front-loaded, but it is too brief to be considered optimally structured. It earns its place by stating the core purpose, but lacks additional context that would justify the same length.

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 tool has 4 parameters, no output schema, and no annotations, the description is highly incomplete. It fails to mention expected output, error conditions, or usage notes that would help an agent use the tool correctly in context.

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 input schema has 50% description coverage (name and video_id have descriptions), but the tool's description adds no parameter information. It does not clarify the role of shop_id or listing_id beyond what the schema provides, nor does it compensate for the missing descriptions.

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 'Upload a video to a listing' clearly states the action (Upload) and resource (video to a listing), which distinguishes it from sibling tools like etsy_listing_video_delete or etsy_listing_video_get. However, it does not explicitly mention the required shop_id and listing_id, but the name implies the context.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., etsy_listing_image_upload for images), nor does it mention prerequisites, limitations, or typical scenarios.

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