gold_etsy_list_listings

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

With no annotations, the description carries the burden of explaining behavior. It discloses the auth requirement and paid restriction, which is useful, and mentions output fields. However, it does not disclose pagination behavior, error conditions, or the fact that the state parameter can return draft/sold_out listings despite the 'active' wording.

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: the main purpose appears in the first sentence, followed by prerequisites and cost. It contains no fluff, though the 'active' qualifier introduces a small inaccuracy.

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 simple two-optional-parameter list tool, the description covers prerequisites and output fields, which is reasonable. But with no output schema and many sibling tools, it omits pagination details and any guidance about choosing this tool over related listing/inventory tools, making it only partially complete.

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 100%, so the input schema fully documents limit and state, including the default for each. The description adds the returned field list but not additional parameter meaning, so the baseline 3 applies.

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 names the action ('List') and resource ('Etsy listings'), and even notes the returned fields. It is clear and not a tautology, but it does not explicitly distinguish itself from siblings like gold_etsy_get_listing, and its 'active' wording is narrower than the state parameter allows.

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 gives prerequisites ('BYOK ETSY_ACCESS_TOKEN + ETSY_SHOP_ID. PAID ONLY PRO $29.') but no guidance on when to use this tool instead of siblings such as gold_etsy_get_listing or gold_etsy_get_inventory. There are no exclusions or alternative-selection conditions.

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