fb_list_campaigns

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

With no annotations, the description carries full burden but only states 'List ad campaigns inside a Meta Ad Account.' It does not disclose whether pagination is handled, rate limits, error behavior, or read-only nature. The implicit read operation is not explicitly marked, and no behavioral traits are mentioned.

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 description is a single, front-loaded sentence that uses no unnecessary words. It efficiently communicates the core function, earning its place with zero waste.

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 having only 2 parameters and no output schema, the description omits crucial context like whether results are paginated or the format of the returned list. It does not mention the use of the 'limit' parameter for controlling output size, leaving the agent with incomplete information.

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 100%, so baseline is 3. The description does not add any extra meaning beyond the schema's parameter descriptions. While the schema clearly describes 'adAccountId' and 'limit', the description merely restates the action without enriching parameter understanding.

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 clearly states the tool lists ad campaigns within a Meta Ad Account. It uses a specific verb ('List') and resource ('ad campaigns'), and the scope is implied by the required parameter. This sufficiently distinguishes it from sibling tools like fb_create_post or fb_get_insights.

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 provides no guidance on when to use this tool versus alternatives such as fb_get_insights for analytics or fb_api for custom queries. It lacks context about prerequisites or when not to use it, leaving the agent without decision support.

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