meta_ads_pages_list

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

With no annotations, the description discloses that the tool is read-only and details the data sources (/me/accounts and /me/businesses -> owned_pages). It also specifies the output fields. It lacks details on pagination, error conditions, or token scopes, but covers the essential behavioral traits.

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 sentences, each earning its place: one for the action, one for the output, and one for the use cases. No fluff or repetition.

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 there is no output schema or annotations, the description covers the tool's purpose, return fields, and usage context. It does not mention pagination or edge cases, but for a simple list tool it is adequately complete.

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 input schema already describes the single parameter (account_id) with format, optionality, and fallback behavior. The description adds no parameter-specific information, and schema coverage is 100%, so it meets the baseline of 3.

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 tool's purpose: 'Lists Facebook Pages the current access token can manage', with specific details about aggregating personal and business-owned Pages. It also names the return fields (id, name, category), making it 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 'Use this to find a page_id before creating lead forms, boosting posts, or attaching a Page to an ad set's promoted_object', providing clear context. However, it does not mention when not to use it or name alternative tools, so it misses the top score.

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