etsy_add_to_cart

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

Discloses a real behavioral prerequisite (login required), which is useful especially with no annotations present. But it does not disclose side effects, failure modes (e.g., out-of-stock), or what happens after adding, leaving the agent to infer the full behavior.

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?

A single sentence front-loads the action and resource before the prerequisite. Every word earns its place, with no filler or repetition.

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?

With no output schema and no annotations, the description should explain expected outcomes, failure behavior, and how to handle variations/quantity. It only covers the login prerequisite, leaving significant gaps for an agent invoking this mutation tool blind.

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%, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides, which is acceptable but not additive.

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?

States a specific verb ('Add'), a resource ('Etsy shopping cart'), and a prerequisite. The resource clearly distinguishes it from siblings like etsy_add_to_favorites and etsy_checkout, so an agent can tell it apart without opening the schema.

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?

Gives a clear prerequisite ('Requires being logged in') and the resource makes intended use obvious. However, it does not explicitly name alternatives or state when not to use it, missing the top-tier guidance of naming sibling tools.

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