snap_list_pixels

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's '(read-only)' merely restates them. It adds nothing about result volume, pagination, ordering, or what happens when the account has no pixels, so it contributes no behavioral context beyond the structured fields.

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?

A single front-loaded sentence with no filler, so it is easy to parse quickly. The only wasted token is '(read-only)', which duplicates the readOnlyHint annotation.

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 simple list tool with no output schema and no nested objects, the description need not explain return values. However, the undefined behavior of the optional ad_account_id and the lack of any result-shape hint leave an agent guessing at the boundaries of a correct call.

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 single parameter ad_account_id has 0% schema description coverage, so the description must compensate by explaining format or optionality. 'Of the ad account' only loosely hints at the parameter; it does not clarify that the schema marks it optional, what the accepted ID form is, or what account is used when it is omitted.

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 (List) and resource (Snap pixels) with the scope narrowed to an ad account. The resource is distinct from siblings like snap_list_ads and snap_list_creatives, so an agent can select it without ambiguity, though the description does not explicitly name how it differs from those listing tools.

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 when-to-use or when-not-to-use guidance and no mention of alternatives such as snap_list_product_sets or catalog-related tools. The only implied context is that it is scoped to an ad account, which the agent could infer from the tool name alone.

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