list_ad_accounts

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

With no annotations, the description must convey behavior, but it only says 'list ad accounts accessible by the token.' It does not disclose pagination behavior, whether it is read-only, or what happens with parameters like 'after' and 'limit'. 'List' implies a safe operation, but no explicit safety guarantee is given.

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 concise sentence with no filler words, front-loading the key action and resource. However, it is so brief that it omits useful context, but that is more a completeness issue than a conciseness one.

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?

Given the tool has 5 parameters, no annotations, and no output schema, the description is inadequate. It does not explain pagination, field selection, or status filtering, nor does it describe the return format. It provides only the bare minimum statement of purpose.

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 0% and the description mentions none of the 5 parameters. There is no explanation for 'after', 'limit', 'fields', 'ad_account_id', or 'effective_status', leaving the agent to infer their roles solely from names. The description adds no value beyond the schema.

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 'List' with the resource 'ad accounts' and further qualifies it with 'accessible by the token', clearly distinguishing it from the singular 'get_ad_account' sibling. This makes the tool's purpose unambiguous.

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 like get_ad_account or list_campaigns. It only implies 'use this to list ad accounts,' but does not mention exclusions or conditions, 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.