list_ad_accounts

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

No annotations are provided, so the description carries the full burden. It explains pagination via 'limit' and 'after', and lists return fields. It discloses that results are based on the current access token. While it doesn't explicitly state read-only or rate limits, the nature of a list operation is safely implied.

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?

Two sentences front-load the purpose and key information. Every phrase adds value: the action, returned fields, and usage guidance. No 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?

Despite having no output schema, the description fully compensates by listing returned fields. With only two simple parameters and no nested objects, the description covers purpose, parameters, output, and usage guidance adequately.

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% with descriptions for both 'limit' and 'after'. The description adds value beyond the schema by specifying Meta's cap (~500) and default (100) for limit, and the cursor source ('paging.cursors.after') for after, aiding correct parameter usage.

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 verb 'List', the resource 'Meta Ad Accounts', and the scope 'accessible to the current access token'. It enumerates the returned fields and positions itself as the starting point for discovery, distinguishing it from siblings like 'get_ad_account' which fetches a single account.

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 says 'Use this first to discover what you can work with', guiding the agent to invoke it before other account-specific tools. However, it does not explicitly mention when not to use or directly compare to alternatives like 'get_ad_account'.

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