gold_etsy_get_listing

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

No annotations are provided, so the description carries the burden. It discloses important environment constraints ('BYOK', 'PAID ONLY PRO $29') and implies a read-only operation through 'Get'. It does not disclose response format, rate limits, or what happens when credentials/tier requirements are not met.

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 terse and front-loaded with the core verb and resource, followed by critical constraints. It earns every sentence. The abbreviation 'BYOK' and the phrase 'PAID ONLY PRO $29' are somewhat cryptic and slightly hurt clarity, so it is not a perfect score.

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 one-parameter read tool, the core behavior is reasonably specified. However, with no output schema and no annotation context, the description does not define the full return shape beyond 'full detail incl images + tags' and does not say how listing_id should be obtained or how BYOK/paid-tier constraints affect 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?

The schema only defines listing_id as a required string, and the description does not explain what the ID represents or where it comes from. 'one Etsy listing' implies it is the listing identifier, but with 0% schema coverage, the description should have compensated more explicitly.

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 verb ('Get'), a specific resource ('one Etsy listing'), and the scope ('full detail incl images + tags'). This clearly differentiates the tool from siblings like gold_etsy_list_listings, which is plural, and gold_etsy_get_inventory, which is inventory-focused.

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 you need full detail for a single Etsy listing. However, it does not explicitly name alternatives or give exclusion criteria, so an agent must infer the difference from sibling names rather than from explicit routing guidance.

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