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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that: it discloses the detection surface (four named sources) and a non-obvious diagnostic behavior — warning when two different GTM containers are live, which double-counts visits. It omits any note on permissions or what happens when no site is resolvable.

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?

Two sentences, front-loaded with the inspection scope, then the pre-change use case and the double-counting warning. Every clause carries information; the source list is slightly dense but earns its place by defining scope.

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 shape need not be described, and the description still tells the agent what will be found (sources + emitted IDs) and the key risk signal. Missing only edge-case behavior for the optional site_url and any permission prerequisites.

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% for the single site_url parameter, which also has a default of "" and is not required. The description says only "a WordPress site" and never explains how site_url selects the target or what the empty default resolves to, so it fails to compensate for the coverage gap.

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 (see/list) and resource (WordPress tracking tags) and enumerates exactly which sources are inspected: GTM4WP plugin, WPCode snippets, header/footer code, and connector output. An agent can immediately distinguish this read/inspect tool from wordpress_set_tracking and from GTM CRUD tools like list_gtm_tags.

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?

"Run this before changing a measurement tag" gives explicit workflow placement and a clear trigger condition, which is stronger than most siblings. It stops short of naming alternatives (wordpress_set_tracking, site_tag_gateway, conversion_tracking_health) or stating when not to use it.

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