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

Annotations only give destructiveHint=true and idempotentHint=false; the description adds substantial non-obvious behavior: the tracking token is minted, installation is automatic on Framer and Duda but article-injected elsewhere, collection halts on disable, Pro+ entitlement is required, and the first call is destructive-mitigating (returns a summary plus confirmToken). This is exactly the context an agent needs before a destructive, non-idempotent write.

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?

Four tight sentences, front-loaded with the enable/disable effect, then preconditions, then the safety protocol. Slightly dense but each sentence carries distinct information; nothing is padding.

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 compensates by describing what the first call returns (summary and confirmToken). Platform behavior, entitlement gating, destructive semantics, and the confirm flow are all covered, so an agent can invoke this safely without further context.

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 coverage is 67% (site and confirmToken documented, enabled bare). The description adds real semantic value by explaining the confirmToken round-trip in prose ('call again with confirmToken to proceed') and tying it to the first call's returned summary/token, which no single schema field description conveys.

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+resource (enabling/disabling the engagement pixel) and spells out the distinct effects per platform (Framer/Duda site-wide code vs. article injection), which differentiates it from sibling get_pixel_snippet. An agent knows exactly what the tool does and what changes as a result.

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 states the precondition 'Pro+ only' and explains the two-step confirmation protocol, which tells the agent how and when the call is valid. What is missing is explicit routing versus alternatives such as get_pixel_snippet (read the snippet instead of installing it), so the when-not guidance is implied rather than named.

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