etsy_taxonomy_property_scales

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

Annotations already indicate readOnlyHint=true, so the description does not add beyond that. It states the operation (get scales) but does not disclose additional behaviors like authentication needs or response structure. The description is adequate but not enriched beyond purpose.

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 with no waste. Starts with verb and resource, includes example. Perfectly 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?

No output schema, and description does not specify return format (e.g., list of strings). For a simple retrieval tool this may be sufficient, but adding expected output shape would improve completeness. Adequate but not full.

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 50%: scale_id has a description, taxonomy_id does not. The description mentions 'taxonomy property' indirectly explaining taxonomy_id, but does not add further meaning to parameters. Baseline 3 is appropriate as schema does partial work.

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 'Get' and the resource 'scales for a taxonomy property', with concrete examples like 'weight units, dimension units'. This distinguishes it from sibling tools like etsy_taxonomy_properties_get.

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 versus alternatives (e.g., vs getting properties or nodes). The name and description imply it is for retrieving scale values, but there is no when-not-to-use or context about prerequisites.

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