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

Annotations already declare readOnly/idempotent/openWorld, and the description adds genuinely new behavior: results are capped at the first 100 active listings in relevance order, and beyond that the tool reports 'not in the first 100'. It also discloses that results may diverge from what a shopper sees on etsy.com, which matters for interpreting output.

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?

Front-loaded with the core behavior in the first clause, followed by the 100-result cap and a shopper-difference caveat — all sentences carry information. The opening sentence is dense enough that it takes effort to parse, but nothing is redundant.

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 carries the return-value burden and does so: it names the position, the missing words from title/tags, and the sentinel result beyond rank 100. Minor gaps remain (rate limits, what happens if neither url nor shop is resolvable), but an agent has enough to invoke it 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 coverage is 100%, so the baseline is 3; the description goes slightly beyond by clarifying that 'url' targets a single listing while 'shop' targets a shop's listings, matching the either/or wording in the schema. It does not add format examples for the Etsy URL, which keeps it from a 5.

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 precise verb+resource: the rank position of a listing (or shop's listings) for a search phrase, plus which query words are missing from title/tags. This is clearly distinguishable from siblings like etsy_listing_check, etsy_niche_check, or etsy_tag_ideas, which address different questions.

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?

Usage is only implied — an agent can infer you call this to audit keyword ranking for a listing or shop. There is no explicit when-to-use, no named alternative, and no statement of prerequisites such as API key or call cost. The caveat that etsy.com search differs per shopper hints at interpretation limits but not tool selection.

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