etsy_buyer_taxonomy_list

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

The description adds minimal behavioral context beyond the annotations. The readOnlyHint annotation already signals safety; the description only reiterates 'list all' without disclosing potential pagination, result size, or ordering behaviors. It does not contradict 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, front-loaded sentence that efficiently conveys the tool's action and purpose with no wasted words.

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?

For a simple listing operation with no parameters and a readOnlyHint annotation, the description is adequate but lacks details on return format, ordering, or pagination. Without an output schema, the agent may need to infer response structure from context.

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 tool has zero parameters, and the input schema is empty with 100% coverage. According to the guidelines, 0 params baseline is 4. The description appropriately does not need to add parameter details.

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 tool 'List all buyer taxonomy nodes' with a specific verb and resource, and clarifies their purpose as 'categories for browsing/discovery'. This distinguishes it from sibling tools like etsy_buyer_taxonomy_node_get (which retrieves a single node) and etsy_taxonomy_seller_list (seller taxonomy).

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?

The description implies usage for retrieving the full hierarchy of buyer taxonomy nodes for browsing/discovery, but it does not explicitly state when to use this tool versus alternatives, nor does it provide any exclusions or conditions. Usage is implied but not guided.

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