gold_etsy_assign_shipping_profile

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

With no annotations, the description carries the full burden, and it does add genuine behavioral context: BYOK (the caller must supply their own key) and a Pro-subscription paywall ($29) that would cause calls to fail without entitlement. It omits the CONFIRM execution gate, idempotency, and error behavior, but those disclosures go beyond the schema.

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?

Three short, front-loaded fragments with no filler: action, use case, then operational constraints. The scope limitation ('in one call') is stated up front, and every fragment earns its place at under 30 words.

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 mutation tool with no annotations and no output schema, the description should disclose return behavior, failure modes, and gating mechanics. It does not mention that confirm=CONFIRM is required to execute (only discoverable in the schema) and says nothing about what happens on success or error, so an agent could make an ineffective first call.

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 33% — only confirm is documented — so the description must compensate for listing_id and shipping_profile_id. It maps them loosely by mentioning 'listing' and 'shipping profile,' but offers no guidance on sourcing valid IDs, expected formats, or how the confirm enum gates execution, leaving two of three parameters effectively undocumented.

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 names a specific verb and resource — 'Set one listing's shipping profile' — and bounds the scope to a single call, making it immediately distinguishable from siblings like gold_etsy_shipping_profiles (retrieval) and gold_etsy_update_listing (multi-attribute updates). The parenthetical use case ('fix this listing has no shipping errors at scale') sharpens the purpose further.

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 provides an explicit trigger scenario — fixing listings that report no shipping profile — which tells an agent when to reach for this tool. It never names alternatives or exclusion conditions, so when-not-to-use logic is left to inference rather than stated.

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