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

Annotations already declare this a safe read operation, so the description only needs to add scope. It does: it discloses that the audit covers both pixel status/events and conversion-optimised campaigns with zero reported conversions, which tells the agent what a result set contains. It does not discuss result size, truncation, or what happens when no pixel exists.

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 tight sentences: the first states what is inspected, the second states the question it answers. Nothing is duplicated or padded.

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?

With four optional parameters, no output schema, and flat structure, the description conveys enough for correct invocation: it frames both the data gathered and the diagnostic intent. A short note on output shape or empty-result behaviour would make it fully complete.

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 each parameter already has a thorough description, including the summary/full enum trade-off and the language hint. The description adds nothing about parameter behaviour, so the baseline of 3 applies.

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 names the specific resource (TikTok Pixels) and the two things it checks: pixel status/events and campaigns optimising for conversions that report none. That is more than a restated title and is clearly distinct from listing tools like snapchat_pixels. It stops short of explicitly contrasting with sibling audit tools such as ga4_tracking_check or gtm_audit.

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 supplies a concrete trigger phrase — 'why no purchases/leads' questions — that tells an agent exactly when to reach for this tool. There is no explicit when-not guidance or named alternative for related diagnostic scenarios.

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