List Offline Event Sets

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by stating the return contents (IDs, names, configuration) and documenting the pagination cursor ('after') and limit default/range, which clarifies the behavior of pagination and result limits.

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 structure is efficient and front-loaded: the purpose is in the first sentence, followed by a brief explanatory context, a labeled Args list, and a Returns line. The explanatory sentence about offline event sets is informative but not strictly necessary for invocation; still, it earns its place by aiding domain understanding.

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 no output schema, the description explicitly lists what is returned (IDs, names, configuration). It covers all front-line parameters (ad_account_id, limit, after) with enough detail, and response_format is documented in the schema. Annotations handle the safety/disclosure burden, leaving no obvious gaps for an agent to call the tool correctly.

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 only 25%, but the description compensates well: it explains ad_account_id (with example), limit (range and default), and after (pagination cursor). The only parameter not covered in the description is response_format, but the schema fully describes that. Thus the description provides essential meaning for all critical parameters.

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 first sentence clearly states the verb ('Lists') and resource ('offline conversion event sets'), and scopes it to an ad account. The additional context about offline events tracking in-store purchases and phone orders distinguishes this from other list tools like meta_list_custom_conversions or meta_list_pixels.

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 gives useful context about what offline event sets are, implying when to use this tool. However, it does not explicitly mention when NOT to use it or name alternatives (e.g., meta_send_offline_event for sending events). Usage is inferred from the purpose rather than articulated.

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