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

Adds non-obvious behavior beyond annotations: each call ADDS a tile and never replaces existing ones (idempotency warning), duplicates are possible, and the product must belong to the linked account. Annotations only say readOnlyHint=false, openWorldHint=false, destructiveHint=false, so this description carries meaningful extra context about side effects and scoping.

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?

Front-loads the core action and effect, then packs prerequisites, duplicate warning, and removal path into two tight sentences. No filler.

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 3-param mutation tool with no output schema, the description covers purpose, required input source, side effects, duplicate risk, and cleanup alternative. Nothing an agent needs to call it correctly is 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 100%, so the schema already documents all 3 parameters including smartsiteId default and carouselTitle maxLength. The description clarifies where templateId comes from, which is slightly useful, but doesn't add syntax or format details beyond the schema. Baseline 3 is appropriate.

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 ('Show an existing product on the linked account's SmartSite as a tile visitors can buy from'), distinguishing it from siblings by describing the visible effect. An agent can tell this apart from swop_add_link or swop_create_product without opening their schemas.

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?

Explicitly names where to get the required id (swop_create_product, swop_list_my_products), warns to check swop_get_my_smartsite to avoid duplicates, and points to swop_remove_link for removal. Covers when, prerequisites, and alternatives.

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