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

Despite annotations already declaring it read-only and idempotent, the description adds substantial behavioral context beyond them: the 50-event / ~15-minute window, the pixel_sdk vs server_to_server channel labels, that an empty list only means nothing arrived in that window, and that a 404 is surfaced when OpenAI has not enabled the stream. It also distinguishes standard (usable as a campaign goal) from custom (measure-only) events.

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 content is dense but well ordered: purpose first, then the questions it answers, then the caveats about the test stream and 404. No sentence is filler, though the parenthetical channel details make it longer than strictly necessary.

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 no explanation, and the description covers the important edge cases (empty window, disabled stream). The one real gap is that the `account` parameter is never addressed, leaving the agent to infer which account is queried.

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% and neither parameter is named in the description; the `account` parameter is never explained at all. The discussion of recent events implicitly maps to `check_recent_events`, but the description does not compensate for the documentation gap on account scoping or on how the two parameters interact.

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 and resource set: it shows conversion tracking pixels (data sources), event settings and their attached campaigns, plus recently received events. That is much more specific than the title. It does not, however, explicitly differentiate itself from near-siblings like chatgpt_ads_details or conversion_tracking_health, so a 4 rather than a 5.

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 concrete usage contexts in the form of the questions it answers ("is my pixel firing", "which campaigns measure which action"), which tells the agent when to reach for it. It stops short of naming an alternative tool or stating when not to use it, so no exclusions are provided.

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