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

Annotations only indicate mutation (readOnlyHint=false) and non-destructiveness (destructiveHint=false). The description adds useful behavioral context by explaining the effect: the product becomes visible to visitors and can be bought. This goes beyond the structured annotations, though it stops short of describing result/error behavior.

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 short, front-loaded with the main action, and clearly communicates the required sequence. There is minor redundancy in mentioning swop_create_product multiple times, but no wasted sentences.

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 simple mutation tool with 3 parameters, the description covers the main action, prerequisite, and key parameter. With no output schema, it does not describe the return value or confirmation behavior, but this is a minor gap given the low complexity of the tool.

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 100% and the schema already documents templateId, smartsiteId, and carouselTitle with meaningful descriptions. The description reinforces that templateId comes from swop_create_product, but adds little beyond the schema.

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: putting an already-created product onto the SmartSite as a visible, purchasable product tile. It clearly differentiates this from sibling tools like swop_create_product by emphasizing that the product must already exist.

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?

It explicitly identifies the prerequisite tool and sequence: 'Use swop_create_product first to make the product, then this to display it.' This gives an agent unambiguous guidance on when to call this tool versus the related creation tool.

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