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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds only the 'snapshot read' qualifier, hinting at point-in-time/cached semantics but not explaining freshness, pagination, or result limits. A modest addition on top of annotations.

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?

A single tight sentence with the scope qualifier front-loaded after the verb. No filler, no redundancy, easy to scan.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. However, the undocumented connection_context parameter and the absence of any routing guidance against similar page/account listing tools leave gaps for a tool in a dense sibling namespace.

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 description coverage is 0% for 2 parameters, so the description carries the burden. It only loosely gestures at ad_account_id ('on one ad account') with no format details, and connection_context is never mentioned anywhere, leaving a required-looking contextual parameter entirely undocumented.

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?

States a specific verb (List) and resource (pages eligible for ad creation) scoped to one ad account. It does not explicitly differentiate from near-siblings such as assets_list_pages, but the 'eligible for ad creation' framing gives it a distinct purpose an agent can recognize.

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?

There is no guidance on when to prefer this tool over assets_list_pages or accounts_list_instagram_accounts, nor any stated prerequisites or exclusions. The phrase 'on one ad account' only implies that an ad account context is required, which the schema already enforces.

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