meta_ads_campaigns_list

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

Declares read-only, describes default status set (non-DELETED), and explains limit behavior with Meta Graph API cap. No annotations provided, but description covers key behavioral traits adequately.

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 sentences, front-loaded with key purpose, no redundant information. 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?

For a list tool with no output schema, description fully covers returned fields, default behavior, and usage context. No missing details for intended use.

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 has 100% coverage with descriptions for all 3 params. Description adds value by explaining fallback for account_id, default for status_filter, and limit cap context.

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?

Explicitly states it lists campaigns with optional status filtering, and names the returned fields. Clearly distinguishes from sibling tools like meta_ads_campaigns_get and pause/enable helpers.

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?

Provides clear guidance: use this to find campaign_id before calling campaigns.get or pause/enable helpers. Also explains status filter options and default behavior.

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