List Campaigns

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

Adds value beyond annotations by detailing return fields (campaign names, objectives, status, budget info) and pagination support with 'after' parameter. Annotations already indicate read-only, non-destructive behavior, and the description aligns without contradiction.

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?

Concise, front-loaded with purpose, and lists parameters clearly. Could be more structured with formatting (e.g., bullet points) but effectively communicates essential details without redundancy.

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 read-only list operation, the description adequately covers inputs, outputs, and pagination. Lacks mention of rate limits or permissions, but annotations address safety. No output schema, yet return fields are summarized.

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 coverage is high (80%), but the description covers 3 of 4 documented parameters with additional context (e.g., example ad_account_id, default value for limit). Missing description for 'response_format' parameter, which is in schema but not in description.

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?

Clearly states it lists campaigns for a Meta ad account, specifying the input parameters and return fields. Differentiates from single-campaign tools like meta_get_campaign but does not explicitly differentiate from other list tools like meta_list_ads or meta_list_adsets.

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?

No explicit guidance on when to use this tool versus alternatives such as meta_get_campaign for a single campaign or meta_get_campaign_insights for performance data. Does not mention prerequisites like having a valid ad_account_id.

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