Update product (offer) availability by id

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

The annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact -- the rate limit of 100 requests / 10 seconds per shop -- but says nothing about what the mutation affects, permission needs, or how the `confirm` requirement works.

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?

It is short and the rate-limit notice is front-loaded, with zero filler. However, the bulk of the text is an operational note rather than task description, leaving the core statement to a single clause.

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?

This is a destructive mutation with 6 parameters, a nested payload object, a payload_file alternative, and a `confirm` approval flag, and there is no output schema to lean on. The description explains none of this complexity or the mutation's blast radius, leaving the agent under-informed for a destructive operation.

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 83%, so the schema itself documents product_id, account, confirm, payload, and payload_file. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 and resource: 'Updates a product (offer) availability'. It is clear what the tool does, but it offers no differentiation from closely related siblings such as update_product_state or update_collection_availability. Note also that the tool name says 'toggle' while the payload takes an explicit `available` boolean, a mild inconsistency the description does not resolve.

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?

There is no guidance on when to use this tool versus any alternative, and no prerequisites or conditions for use are given. With siblings like update_product_state and update_collection_availability in the same namespace, the absence of routing guidance is a real gap.

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