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

The annotations already establish that this is a read-only, non-destructive, open-world operation, so the description only needs to add context. It does add that pixel ID and status are the relevant data, but it does not explain what is returned beyond that or how the account/folder scoping behaves.

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?

It is short, but the opening is awkward and the second sentence about pixel goals is not clearly tied to this tool's behavior. Some wording does not earn its place.

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 read-only pixel-listing tool with complete schema coverage and annotations, the description should at least clearly say it lists pixels and their statuses. Instead, it introduces an undocumented pixel_id requirement and leaves the actual retrieval behavior underspecified.

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 100%, so the schema already documents folder, account, and language. The description instead introduces a 'pixel_id' that is not a parameter in the schema, which is misleading and adds confusion rather than meaning.

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 never states a clear verb such as 'list' or 'get'; 'Snap Pixels on the ad account with ID and status' reads as a restatement of the title rather than a definition of the action. An agent can infer it retrieves pixel IDs and statuses, but the purpose is not stated unambiguously.

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 guidance on when to use this tool, what prerequisites exist, or how it relates to sibling Snapchat tools. The note that pixel goals need a pixel_id does not explain where to obtain one or whether this tool supplies it.

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