etsy_call

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

With no annotations provided, the description carries the full behavioral disclosure burden. It does offer a useful insight: Etsy scope refusals can masquerade as permission errors. But it fails to disclose that the tool can invoke mutating operations, requires authentication/scopes, or returns operation-dependent response shapes. These are material gaps for a generic dispatcher.

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?

Two short sentences deliver the core purpose first, then add a targeted troubleshooting hint. There is no filler, restatement, or redundant detail. The structure is front-loaded and every word earns its place.

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 generic dispatch tool with no output schema and no annotations, this definition is incomplete. It omits how to obtain valid operation ids, how body and params should be shaped, what response variability to expect, and whether operations can have side effects. The 403 scope hint helps but leaves too many invocation details unexplained.

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 0%, so the description must compensate for the schema's silence. It only clarifies operation_id ('by id'). The body and params objects receive no explanation of how they correspond to Etsy API path, query, or body arguments. This is insufficient for an agent to confidently construct a request.

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 states a specific verb ('Call'), a clear resource ('any Etsy operation'), and the key selection criterion ('by id'). This immediately distinguishes it from the sibling tools, which are named for specific operations (e.g., etsy_get_listing, etsy_list_receipts), making it clear this is the generic dispatcher.

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 use when an operation id is available and provides a conditional fallback to etsy_check_scopes on 403. However, it does not explicitly state when to prefer dedicated sibling tools over this generic call, nor does it mention discovering valid operation ids via etsy_list_operations. Normal selection guidance is only implied, not explicit.

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