ad_manager_fb_upsert_pixel

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

Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false, which align with an upsert operation. However, the description adds no additional behavioral context—it doesn't explain what happens to existing pixels, any side effects, or permission requirements. It neither contradicts nor enriches the annotations, so it provides minimal value beyond what annotations already convey.

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?

While the description is extremely concise (a single phrase), it is under-specified rather than efficiently concise. It lacks any explanatory structure or front-loaded key information. The phrase 'Upsert conversion pixel' is not a useful summary; it is merely a restatement of the name, failing to convey any actionable details.

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 mutation operation with 5 parameters and no output schema, the description is incomplete. It doesn't explain what an upsert does to existing pixels, what constitutes a valid pixel, or any dependencies (e.g., requires an ad account or integration). The agent has no idea what to expect in terms of return values or side effects, making the tool difficult to invoke 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?

The schema covers all 5 parameters with descriptions, achieving 100% coverage. The description adds no parameter-specific semantics, so it relies entirely on the schema. Given the high schema coverage, the baseline score of 3 is appropriate.

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 'Upsert conversion pixel' is essentially the tool name with spaces inserted. It restates the name without adding any specificity about what an upsert entails, what a conversion pixel is, or how it differs from sibling tools like ad_manager_fb_get_pixels or ad_manager_fb_upsert_ad. This is a tautological restatement rather than a clear explanation of purpose.

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 description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, conditions, or scenarios where one might use get_pixels for reading or create_integration for setup. The agent is left without any contextual instructions to select this tool appropriately.

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