etsy_listings_list_by_shop

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

Annotations indicate readOnlyHint=true, so the safe-read nature is known. The description adds 'all listings' but fails to mention pagination, default state filtering, or that it requires shop access. Limited behavioral disclosure 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 very concise (one sentence). However, it sacrifices necessary details for brevity. It is front-loaded but incomplete.

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 7 parameters, no output schema, and is a paginated list endpoint, the description lacks pagination, sorting, filtering options, and return format. It is far from complete for effective use.

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 only 14% (only shop_id described). The description adds no parameter details. With low coverage, the description should compensate but does not. No parameter meaning is conveyed.

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 it lists all listings for a specific shop. The verb 'list' and resource 'listings belonging to a specific shop' are precise. However, it does not explicitly differentiate from the sibling tool 'etsy_listings_list', which might list all listings without per-shop filtering, so it loses a point.

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 explicit guidance on when to use this tool over alternatives. It only implies usage when needing listings for a specific shop, but no mention of when not to use it, prerequisites, or alternatives like 'etsy_listings_list'.

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