list_pixels

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about permissions needed, pagination defaults, whether results span all websites, or what is returned. 'List' weakly implies a read-only operation, but that is the extent of the behavioral signal.

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?

The single short phrase is free of waste and front-loaded, but the brevity reflects under-specification rather than efficient communication. There is nothing to structure, so it neither helps nor hurts beyond being minimal.

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?

With five undocumented parameters, no annotations, and no output schema, the description supplies none of the information an agent needs to invoke this correctly. It is inadequate for a tool of this parameter complexity.

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?

Five parameters (page, search, orderBy, pageSize, sortDescending) have 0% schema description coverage, and the description mentions none of them. An agent must guess at pagination semantics, default ordering, and whether 'search' matches name, URL, or ID.

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 phrase "List tracking pixels" names a specific verb (List) and resource (tracking pixels), so an agent immediately knows the operation. It does not differentiate from siblings like list_team_pixels, get_pixel, or get_pixel_charts, leaving ambiguity about scope (all pixels vs. team vs. website).

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 versus list_team_pixels or get_pixel, nor any stated prerequisites (e.g., website/team context). The only implied usage is the verb 'list' itself.

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