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

No annotations are provided, so the description carries the full behavioral disclosure burden. It indicates a list/read operation but does not mention pagination behavior via cursor/limit, response shape, or any side effects—gaps an agent must resolve elsewhere.

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. Every word contributes to purpose or context, making it efficient and easy to parse.

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 tool with no annotations and no output schema, the description is too thin. It omits pagination expectations, return value structure, and explicit relationship to sibling tools, leaving an agent to guess at response behavior.

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%, and the description only contextualizes the overall resource rather than explaining individual parameters. pixel_id is implied by 'Meta pixel,' but limit and cursor receive no semantic clarification beyond the schema's type/default/min/max information.

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 uses a specific verb ('List'), names the resource ('conversion events for a Meta pixel'), and states the purpose ('for ad set optimization'). This clearly distinguishes it from sibling tools like get_pixel_details or list_custom_conversions.

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 phrase 'for ad set optimization' implies when the tool is useful, but it does not explicitly state when to prefer it over alternatives such as adsap_get_pixel_stats or adsap_list_custom_conversions. There is no exclusion guidance.

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