etsy_user_favorite_listings_list

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

Annotations already indicate readOnlyHint=true, and the description confirms it lists favorites. However, it does not disclose additional behavioral traits like pagination, default ordering, or what happens if the user has no favorites. Description adds minimal value beyond annotations.

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, precise sentence with no unnecessary words. It is appropriately short and front-loaded with the key information.

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 three parameters, no output schema, and no parameter descriptions, the description is insufficient. The agent needs to know pagination behavior (default limit, max, offset), what the response format is, and how to handle large datasets. The current description leaves all of this undefined.

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 description does not explain any of the three parameters (limit, offset, user_id). With 0% schema description coverage, the description was expected to compensate but fails entirely. Agents get no insight into what these parameters mean or how to use them.

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 action 'List' and the resource 'a user's favorited listings'. It distinguishes from sibling tools like etsy_user_favorite_listing_add, _get, and _remove, as well as other listing-related tools.

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 on when to use this tool vs alternatives, no prerequisites mentioned (e.g., user_id must be valid), nor when to avoid using it. Agents have no context for choosing this over etsy_user_favorite_listing_get or other listing tools.

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