Tracking setup summary

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

No annotations are provided, so the description carries the transparency burden. It clearly discloses the output's content and perspective (plain-language, marketing-focused) and mentions surfacing issues for the dev team. It does not state whether the tool performs a live fetch or side effects, but 'summary' strongly implies a read-only operation.

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?

One sentence with a colon-separated list packs high information density without fluff. It is front-loaded with the key purpose and intended audience.

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 one-parameter tool, the description fully explains the deliverable and topics covered. It lacks return-format details and usage timing, but those are partially covered by the simple parameter and sibling context, making it adequate though not exhaustive.

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?

With a single parameter and 100% schema coverage, the schema already defines 'url' as an absolute http(s) URL to audit. The tool description itself adds no further parameter-level detail, which is acceptable given the schema's completeness.

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?

Description opens with 'Plain-language summary' naming the deliverable and audience (media buyer/marketer), and enumerates content areas: installed tracking, campaign implications, consent posture, and dev-team issues. This clearly distinguishes it from sibling tag-detection or performance-audit tools by its synthesizing role.

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?

No explicit when-to-use or when-not-to-use is stated, nor are alternative tools named. The audience and purpose are clear enough to imply use when a non-technical, synthesized summary is needed, but there is no exclusion guidance against using related tools like detect_tracking_tags.

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