update_pixel

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

With no annotations provided, the description carries the full burden and discloses almost nothing. It does not say whether the update is partial or full-replacement (e.g. whether omitting `slug` clears it), whether auth/ownership is required, or whether changes are reversible — all material for a mutation tool.

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?

Four words, front-loaded, zero padding — but that brevity is under-specification rather than economy. There is nothing to trim, yet nothing was added either.

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?

The tool is structurally simple (flat, 3 params, 1 required, no output schema), so it does not need a long description — but for a mutation tool with zero annotation coverage and zero schema descriptions, an agent still cannot determine what is updatable or what response to expect. It falls short of the minimum needed to call this 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 must compensate and it does not: neither `pixelId` (the sole required field) nor the mutable `name`/`slug` fields are mentioned. The schema's minLength/maxLength constraints on slug are also unexplained (e.g. why 8 chars minimum).

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 ("Update") and resource ("tracking pixel"), so the agent knows the action class. But it gives no indication of which attributes are mutable or how this differs from sibling mutators like update_website or update_link beyond the resource name.

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?

No guidance on when to use this versus create_pixel, get_pixel, or delete_pixel, and no stated prerequisites such as required permissions or ownership. The agent must infer everything from the sibling list.

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