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

Annotations already establish readOnly, idempotent, non-destructive, open-world behavior, so the description's job is lighter. It adds real value by disclosing what data are fetched, that Etsy's published title/tag rules are applied, and the notable output contract that only the *first* thing to fix is returned rather than a full report.

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?

Three sentences, with the resource and returned fields front-loaded before the usage triggers. The field enumeration is somewhat list-heavy but each item conveys what the agent can expect back, so little is wasted.

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?

With no output schema, the description correctly carries the burden of describing returns (field set plus the 'first thing to fix' result), and it supplies use cases and rule application. Nothing material for correct invocation is missing.

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% with a single required parameter already documented as an Etsy listing link or listing number. The description adds no parsing details, accepted variants, or error behavior beyond the schema, so 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?

States a specific verb and resource ('Reads one Etsy listing from Etsy's API') and enumerates the returned fields (title, tags, photos, video, expiry, renew, favorites, AI mention). This is clearly distinct from siblings like etsy_shop_audit or etsy_rank_check, which operate on different subjects.

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?

Provides concrete trigger phrases ('is my listing set up right?', 'when does my listing expire?') that map intent to this tool. It does not explicitly exclude or reference alternatives such as etsy_shop_audit for shop-level checks, so routing at the boundary is left to inference.

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