get_pixel

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

With no annotations, the description carries the full burden of disclosure, and four words disclose nothing: not whether pixelId must belong to a website the caller can access, not what happens on an unknown ID, not whether the pixel record is read-only or includes a writable snippet. This is a lookup tool whose failure and return behavior are entirely undocumented.

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 contain no filler and are trivially front-loaded, so nothing needs trimming. The brevity is under-specification rather than disciplined conciseness, which caps the score.

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?

A single-parameter lookup is simple, but with no annotations and no output schema, the description is the only place an agent could learn what comes back and what access is required. It supplies neither, leaving the definition insufficient for confident invocation.

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 should compensate for the single undocumented parameter, but it adds nothing about pixelId beyond what the schema already shows (a required uuid). The agent must infer that pixelId is the pixel's own identifier rather than, say, a website 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?

"Get a tracking pixel" names a verb and a resource and clarifies that the domain is analytics tracking pixels, but it is essentially a restatement of the name. It does not say whether the returned object is the pixel's configuration, its embed snippet, or its status, nor does it distinguish it from list_pixels or get_pixel_charts.

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 call this versus list_pixels (for enumeration) or get_pixel_charts (for reporting). No prerequisites such as needing a website ID or a pixel belonging to an accessible website are mentioned.

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