get_pixels

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely states 'Fetch pixels' but does not mention that it is a read-only operation, that it returns a paginated list, or any default behavior. This is insufficient for a tool with no annotation support.

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 description is a single sentence with no wasted words. However, it is under-specified and could include more useful context without becoming verbose. For a simple tool, it is concise but not as informative as it could be.

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 has only 2 parameters with full schema coverage, and no output schema. The description is minimal and does not explicitly state that it returns a paginated list of pixels or clarify the default limit, but the plural 'pixels' and pagination params imply this. It is adequate for a simple fetch but leaves room for improvement.

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 input schema fully describes both parameters ('after' and 'first') with clear descriptions, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides, which is acceptable given the high schema coverage.

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 verb 'Fetch' and resource 'pixels' clearly indicate the action and target. However, it doesn't explicitly differentiate from sibling tools like get_custom_pixels or get_pixel, though the plural 'pixels' and the name itself help. It's clear but lacks scope specificity like 'all' or 'list'.

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 such as get_pixel for a single pixel or get_custom_pixels for custom pixels. No use case or exclusions are mentioned, leaving the agent without context for selection.

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