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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, and the description adds substantial context beyond them: a WPCode snippet is switched off rather than deleted, a theme-hard-coded id is reported back under skipped with file and line, head_code="" clears emitted code, and confirm=false previews match counts while writing nothing. It also documents the already_applied/skip behavior that makes reruns safe.

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 scope statement is front-loaded and each subsequent paragraph addresses a distinct mode (set id, remove id, clear header, surgical replace), so the length is mostly earned. It is dense prose without headers or bullets, which makes the 11-parameter surface harder to scan than it needs to be.

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?

An output schema exists, so return values need not be described, and the description thoroughly covers the destructive paths, verification semantics, and the follow-up removal step. The remaining gap is the unexplained snippet-enable/disable and site-selection parameters, which matter for a tool with 0% schema coverage.

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 0% across 11 parameters, so the description carries the full explanatory burden. It covers gtm_id, remove_id, head_code, replace, replace_in and confirm well, but leaves enable_snippet, disable_snippet and site_url entirely unexplained and never names ga4_id explicitly (only 'GA4 measurement id').

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 first sentence states a specific verb (set) plus the resource (a WordPress site's GTM or GA4 measurement id, header code, or an old tracking snippet) and enumerates the distinct operating modes. An agent can differentiate it from siblings such as wordpress_tracking or site_tag_gateway without opening the schema.

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 gives strong context for the remove_id path ('This is how you stop a site double-counting after a container change') and routes hard-coded theme copies to wordpress_theme_file(mode="remove_block"). It does not, however, say when to prefer this tool over the read/list counterparts (wordpress_tracking) or over connect_tag_manager/connect_ga4, so a little routing inference is left to the agent.

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