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

Annotations only provide openWorldHint, so the description carries the full burden and does so: it discloses the `rejected` response shape (machine-readable reason plus echoed allowed values), the `unset_required` follow-up field, and that existing listings pick these up on their next sync. It also warns that these are legally-weighted merchant attestations and instructs on failure modes (leave unset rather than invent).

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 long and uses heavy emphasis markers, but it is well front-loaded: the scope and the primary alternative come first, then the per-product exclusion, then the legal-attestation warning. Every block carries actionable content, though the legal warning is repeated at length and could be tightened without losing meaning.

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, the description still explains the relevant return behaviors (`rejected`, `unset_required`) and the deferred-application timing. For a 5-param nested-object mutation tool with only openWorldHint annotation coverage, nothing an agent needs to call it correctly appears to be missing.

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 only 40% across 5 params, so the description must compensate. It does add real meaning for `values` (setting key -> value exactly as the merchant supplied it, object form for value_type "object") and for `integration_uuid` (used with describe_listing_attributes to discover channel settings), but `remove`, `workspace`, and `store_uuid` get no semantic elaboration.

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 and resource with explicit scope: 'Set SHOP-WIDE listing settings for one connected sales channel', then enumerates the setting families (compliance attestations, shipping template, fallback size chart). It explicitly contrasts itself with set_listing_attributes for the per-product settings, so an agent can distinguish it from that sibling immediately.

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 concrete when-to-use and when-not-to-use guidance: call describe_listing_attributes with `integration_uuid` and no `product_uuid` first, use set_listing_attributes for BRAND and per-listing size charts, and set `default_size_measurements` only when the whole catalogue is one blank. Alternatives and preconditions are named rather than implied.

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