gold_etsy_create_listing

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

With no annotations provided, the description carries the transparency burden. It discloses that the tool creates a draft rather than a published listing, and it flags important prerequisites via 'BYOK' and 'PAID ONLY PRO $29'. This is useful behavioral context beyond the tool name, though the acronyms could be unclear.

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 short and front-loaded with the core purpose, followed by the critical requirements. The format 'BYOK. PAID ONLY PRO $29.' is terse but efficient, sacrificing some clarity for brevity.

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 tool with 10 parameters, no output schema, and minimal schema descriptions, the description is incomplete. It covers the primary required fields and the paid/auth requirement, but it leaves confirm semantics, optional parameters, category_id mapping, and expected results undocumented, making the tool harder to invoke correctly.

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 only 10%, so the description must compensate. It lists several key parameters (title, description, price, quantity, who_made, when_made, category), which helps identify the main inputs. However, it uses 'category' while the schema has 'category_id', and it omits confirm, return_policy_id, and shipping_profile_id, so it only partially clarifies parameter semantics.

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 states a specific action and resource: 'Create a draft Etsy listing', and enumerates the key fields involved. It clearly differentiates this from sibling tools like update_listing, get_listing, or list_listings by the 'create' verb and 'draft' qualifier.

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 when to use the tool: when creating a new draft Etsy listing, as opposed to updating an existing one. It also adds an eligibility constraint with 'PAID ONLY PRO $29', but it does not explicitly name alternatives or state when not to use it.

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