etsy_listing_feature

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action (feature) and rank, but does not mention whether the operation is destructive, idempotent, what happens if the listing is already featured, or if special permissions are needed. This is insufficient for a mutation tool.

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 a single sentence of 8 words, which is too brief to adequately inform the agent. Important details about parameters, behavior, and usage are missing, making it under-specified rather than concise.

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?

Given the tool has 3 parameters, no annotations, and no output schema, the description is severely incomplete. It does not cover return values, error conditions, prerequisites (e.g., shop must exist, listing must be active), or any side effects, leaving critical gaps for the agent.

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 0%, so the description should add meaning to parameters. It mentions 'rank' but does not explain that it must be between 1 and 4, nor does it elaborate on the roles of 'shop_id' and 'listing_id'. The agent gains little beyond the raw parameter names.

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 clearly states the verb 'Feature' and the resource 'a listing at a specific rank in the shop', making its purpose apparent. However, it does not explicitly distinguish from the sibling tool 'etsy_listing_set_featured_rank', which might have overlapping functionality, so it is not a perfect 5.

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?

No guidance is given about when to use this tool versus other listing manipulation tools like 'etsy_listing_unfeature' or 'etsy_listing_set_featured_rank'. There is no information on prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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