meta_ads_campaigns_list

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

States the tool is read-only and notes Meta Graph API pagination caps. However, does not mention potential authentication requirements, rate limits, or behavior when account_id is omitted (fallback to env variable is only in schema description). Without annotations, more details on side effects or prerequisites would be beneficial.

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?

Highly concise: two information-dense sentences that cover purpose, returned fields, usage hint, and alternative tool. No fluff, every sentence adds value.

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?

Despite no output schema, the description lists all returned fields. For a list tool with 3 optional parameters, the description covers purpose, usage, behavioral constraints (read-only, pagination limit), and distinguishes from siblings. Complete and actionable.

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 100% (all parameters described in schema). The description adds context: account_id format and fallback, limit cap and Meta API limits. This extra detail goes beyond the schema, justifying a score above baseline 3.

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?

Description clearly states the tool lists campaigns with optional filtering, enumerates returned fields, and distinguishes from meta_ads_campaigns_get and pause/enable helpers, leaving no ambiguity about its function.

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?

Explicitly tells the agent to use this to find a campaign_id before calling get/pause/enable helpers, and notes that for a single campaign's full detail, use meta_ads_campaigns_get. Also provides limit handling advice.

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