audience_create_pixel

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is partly covered. The description does add a nuance beyond that: a timed-out/uncertain call must not be blindly retried. But it leaves 'guarded' undefined and never explains the confirmation mechanism or whether the pixel is usable immediately.

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?

A single compact sentence with the operation front-loaded and no filler. It loses a point because the compressed phrasing ('guarded') is cryptic rather than informative at this length.

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 not be explained, but for a write tool with three fully undocumented required parameters, no prerequisite flow, and no recovery path for uncertain outcomes, the description is far too thin to let an agent invoke it correctly.

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 all three parameters (name, idempotency_key, confirmation_hash) are required and undocumented anywhere. The description only obliquely gestures at idempotency semantics and says nothing about what confirmation_hash is, where it comes from, or the format/uniqueness rules for idempotency_key.

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 concrete verb+resource ('create' a 'tracking-pixel'), which distinguishes it from the geo_circle/geo_polygon/pixel_viewers siblings. However, it never distinguishes itself from the closely related audience_validate_create or audience_reconcile_create, which an agent would need to sequence around this call.

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?

There is no explicit when-to-use guidance, no mention that a validate step or confirmation_hash must be obtained first, and no pointer to audience_reconcile_create for ambiguous outcomes. The phrase 'uncertain outcomes are not resent' is a behavioral note, not usage routing.

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