Fan one stored event out to every enabled conversion integration (202)

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

Annotations already declare a non-read-only, open-world mutation, and the description usefully adds the 202-style fan-out behavior plus the fact that omitting confirm returns a preview and that no server-side dry run exists. It does not disclose what the 202 response contains at the delivery level, whether fan-out is partial-failure tolerant, or whether idempotency matters for retries — meaningful gaps for a fan-out write.

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 dense sentences, front-loaded with the purpose and endpoint, then the write gate — no filler. The stacked parentheticals make it slightly clunky to parse but nothing is redundant with the title.

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 nested-body write with no output schema, the description covers the critical execution gate and the preview return path, which is the highest-value information. It stops short on the fan-out semantics an agent would need — partial failure behavior, per-integration results, and what the consent/adAccountIds fields actually control.

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 67%, so the schema already documents confirm and idempotencyKey; the description only reinforces the confirm gate rather than adding new meaning. The nested body fields (consent, userData identifiers, adAccountIds, sourceUrl) — the parameters most likely to be misused — receive no treatment in the description, which is the main shortfall.

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 a specific verb and resource ("Fan one stored event out to every enabled conversion integration") plus the HTTP operation (POST /v1/conversions/send), so an agent knows exactly what the call does. It implicitly separates itself from conversions_listDeliveries and conversions_requeue, but never names an alternative, so it falls short of full sibling differentiation.

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 only explicit usage constraint is the write gate: nothing is sent unless confirm is true, and there is no server-side dry run. There is no guidance on when to prefer this fan-out over conversions_requeue for redelivery or conversions_setIntegration for configuration; the agent must infer that from the tool names.

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