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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds substantive behavior: the output is byte-for-byte identical to what the dashboard copies, it includes `defer` for Shopify stores, the embedded URL is domain-specific, and a manually constructed tag will not verify. That last point is the kind of consequence disclosure an agent cannot infer from structured fields.

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 tight sentences, front-loaded with what is returned and scoped immediately to a single domain. Every sentence carries a distinct payload — identity, constraint on fidelity, and next step — with 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 single-optional-parameter read tool with an output schema and full annotation coverage, nothing material is missing: the return value needn't be explained, the safety profile is annotated, and the description supplies the domain-specificity and Shopify caveats an agent would otherwise get wrong.

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 explains that domainId selects a domain and that omitting it falls back to the account's default domain. The description restates the 'one domain in the connected account' scope but adds no format, validation, or lookup guidance 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?

States a specific verb and resource — 'Returns the CookiePal banner script tag' — and scopes it to 'one domain in the connected account'. It also implicitly separates itself from verify_installation (named as the follow-up check) and from regenerate_banner (a hand-built or re-generated tag is explicitly called out as not equivalent).

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 clear operating context: use this to obtain the tag to paste into a site, and run verify_installation afterwards to confirm it is live. It also warns against hand-building or cross-copying a tag. It stops short of an explicit 'do not use this when…' exclusion against siblings like regenerate_banner, so it is strong rather than complete.

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