List Meta Ad Accounts

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, lowering the bar. The description adds useful behavioral context: it lists accessible accounts, returns specific fields (IDs prefixed with act_, names, currency, status, spend info), and notes it is the entry point for downstream campaign/insights work.

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?

Three short purposeful sentences: what it does, what it returns, and when to call it. No filler or redundant repetition of the tool name/title.

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 simple listing tool with no required parameters and no output schema, the description is complete: it explains the scope ('all ad accounts accessible to the authenticated user'), the return content, and the recommended usage sequence. An agent has enough to decide when and how to invoke it.

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 the single response_format parameter is fully documented in the schema. The description adds no parameter-specific meaning, but none is needed; the baseline of 3 applies.

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 uses a specific verb ('Lists') with a clear resource ('Meta ad accounts accessible to the authenticated user'), and distinguishes the tool's broad listing scope from siblings like meta_get_ad_account or meta_list_ads. It also states the returned fields, making the tool's purpose unmistakable.

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 explicitly says 'Call this first to get ad account IDs needed for campaign and insights tools,' providing clear context and sequencing. It does not name alternative tools or exclusion conditions, but the guidance is sufficient for this simple listing operation.

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