etsy_listing_video_get

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

Annotations already declare readOnlyHint=true, so the description adds no new behavioral context. It fails to disclose traits like error handling (e.g., what if video or listing doesn't exist) or any side effects. With annotations present, the description should add value beyond them, but it does not.

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 a single concise sentence, but it is under-specified. While it is succinct, it sacrifices essential details for brevity, making it less useful than a slightly longer but more informative description.

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 2 required parameters, a read-only annotation, and no output schema, the description is too minimal. It does not mention what the tool returns, error conditions, or how it relates to sibling video tools. The agent lacks context for successful invocation.

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 0%, and the description does not explain any parameters (listing_id, video_id). The agent must rely solely on the schema names and types, which lack semantic context. The description provides no compensation for this gap.

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 tool retrieves a specific video for a listing, using the verb 'get' and the resource 'specific video'. It distinguishes from sibling tools like etsy_listing_videos_list (lists all) and etsy_listing_video_delete (deletes), making its purpose unambiguous.

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 you have a specific video_id, but it does not explicitly state when to use this tool versus alternatives like etsy_listing_videos_list or provide exclusions. No guidance on prerequisites or context is given.

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