Audit Conversion Tracking Health

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

With no annotations, the description carries the behavioral disclosure burden. It reveals meaningful behavior: inspecting brand approval and event settings, and optionally polling a 15-minute live stream. It does not disclose whether the audit is read-only, what permissions are required, or any side effects, so transparency is partial rather than complete.

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 crisp sentences front-load the purpose ('Comprehensive tracking audit') before detailing the scope. There is no fluff, though 'Comprehensive' is slightly redundant with the enumerated checks that follow.

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?

Given only one optional parameter, no output schema, and no annotations, the description provides enough for an agent to decide when to call it and how to invoke it: what is inspected, the optional live-poll behavior, and the diagnostic intent. Not stating the output/return shape is a minor gap for a diagnostic audit tool.

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 100%, and the schema already documents pixel_id as optional and tied to verifying the live browser event stream. The description reinforces the 15-minute stream behavior but adds no new parameter meaning beyond what the schema provides.

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 uses a specific verb ('audits'/'inspects'), identifies the resource (conversion tracking health), and enumerates concrete checks: brand approval, conversion event settings, and live pixel stream. These specifics distinguish it from narrower siblings like inspect_recent_pixel_events and list_conversion_event_settings.

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?

The description implies use for diagnosing missing events, tag misconfigurations, and CAPI readiness, which gives useful context. However, it never explicitly contrasts this tool with alternatives such as inspect_recent_pixel_events or list_conversion_event_settings, nor does it state 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.