list_ad_accounts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that the tool MUST automatically paginate through all pages, use the facebook_fetch_pagination_url tool, not stop after the first page, and return a consolidated list in a single response. This is exceptionally transparent about the tool's internal behavior and constraints.

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 appropriately structured: it leads with the core purpose, then presents a critical pagination instruction. The wording is somewhat repetitive ('CRITICAL', 'IMMEDIATELY', 'AUTOMATICALLY', 'This is a requirement') but the length is justified by the importance of the pagination behavior. It could be trimmed slightly, but it remains focused.

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 no-parameter tool with an output schema, the description fully covers the essential context. It specifies the action, the required pagination behavior, the dependency on another tool, and the expected consolidated return. There are no missing details that would prevent an agent from invoking it correctly.

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?

The tool has zero parameters, so the schema provides no semantic information. The baseline for 0 parameters is 4, and the description adds nothing beyond confirming that there are no inputs. No parameter explanations are needed, so the score remains at baseline.

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') and resource ('ad accounts and their names') associated with the Facebook account. It is specific enough to distinguish from sibling tools like get_details_of_ad_account or get_ads_by_adaccount, which target individual entities. The wording is 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?

No guidance is given on when to use this tool versus alternatives. There is no mention of exclusions (e.g., 'use get_details_of_ad_account for a single account') or specific scenarios where this tool is preferred. The pagination instruction is behavioral, not about selection criteria.

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