etsy_taxonomy_properties_get

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

The description adds minimal value beyond the annotation (readOnlyHint). It does not disclose any behavioral details such as pagination, result size, or authentication needs. With annotations present, the bar is lower, but the description still lacks useful context.

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?

Single sentence, directly to the point, no fluff or unnecessary 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 simplicity (1 param, no output schema), the description is adequate but incomplete. It does not describe the return format or structure of properties, leaving the agent uninformed about what to expect from the response.

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 100% for the only parameter. The description adds no new meaning beyond what the schema provides (taxonomy_id is a node ID). Baseline 3 is appropriate.

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 retrieves all available properties for a specific taxonomy node, using a specific verb and resource. It distinguishes from sibling tools like 'etsy_taxonomy_node_get' which retrieves a node itself.

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 provided on when to use this tool versus alternatives such as 'etsy_taxonomy_properties_list' or 'etsy_taxonomy_property_scales'. There are no prerequisites or exclusions mentioned.

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