etsy_listing_occasion_set

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

The description does not disclose behavioral traits beyond the action of setting. Since annotations are absent, the description should convey whether the operation is destructive, idempotent, or has side effects, but it does not. This is insufficient for a mutation tool.

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 concise sentence with no fluff. However, its brevity comes at the cost of omitting valuable information. It is appropriately front-loaded but could include more detail without harming clarity.

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 tool's simplicity (setting one attribute) and lack of output schema, the description minimally covers the core action. However, it lacks context about validation, error conditions, or relationship to other listing operations, making it only moderately complete.

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 low (33%), with only 'occasion' having an enum description. The tool description adds no meaning for 'shop_id' or 'listing_id', and does not explain their format or relationship. The enum list in schema helps, but the description fails to compensate for the coverage gap.

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 action ('Set') and the resource ('occasion attribute for a listing'). It is specific and distinguishes the tool from siblings like 'etsy_listing_occasion_get', though it does not highlight how it differs from general update tools.

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 guidelines are provided about when to use this tool versus alternatives like 'etsy_listing_update', nor are any prerequisites (e.g., listing existence, ownership) mentioned. The agent receives no context on appropriate usage.

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