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

Annotations already declare readOnly=false, destructive=false, idempotent=false, so safety is largely covered. The description adds genuinely new behavioral context beyond that: the confirm=false dry-run/staging mode and confirm=true commit, plus the post-creation install requirement.

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?

Front-loaded with purpose and necessity, then next steps, then the confirm flag semantics. Dense and useful, though the em-dash clauses and parenthetical make it slightly longer than strictly needed.

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. The description covers purpose, prerequisites, follow-on steps, and the confirm preview behavior, which is sufficient for an agent to invoke this three-parameter mutation 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%, so the description carries extra burden. It explains confirm's preview-vs-create semantics well, but says nothing about advertiser_id or name, leaving a third of the parameters undocumented anywhere. Partial compensation only.

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 specific verb and resource ('Creates a TikTok conversion PIXEL') and immediately distinguishes it from siblings by naming the listener/consumer tools (send_tiktok_conversion_event, and implicitly list_tiktok_pixels). An agent can route to it without opening any schema.

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?

Gives clear context ('on a fresh account this is the first thing to set up') and a follow-on action (install code or send events server-side). It stops short of explicit exclusions or naming a sibling to prefer instead, so it is clear guidance rather than full when/when-not routing.

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