meta_ads_pages_list

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

With no annotations, the description carries the safety burden and does disclose 'Read-only,' the aggregation of personal and business-owned Pages, and the returned fields. It does not mention pagination or rate limits, but for a list tool the core behavior and output shape are transparent enough.

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?

Every sentence earns its place: main action, output fields, read-only flag, concrete use cases, and sibling differentiation. It is front-loaded with the core purpose and avoids fluff.

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 simple read-only list tool with one optional parameter and no output schema, the description covers purpose, scope, return shape, use cases, and what it does not do. An agent has enough context to invoke it correctly without opening any other tool.

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 schema already documents the only parameter (account_id) at 100% coverage including format, optionality, and fallback, so the description does not need to repeat it. The description adds auth context ('current access token') but not additional meaning specific to the account_id parameter, meriting the baseline score.

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 opens with a specific action and resource: 'Lists Facebook Pages the current access token can manage,' and clarifies it returns id, name, and category. It also contrasts with meta_ads_pages_photos_list so an agent can distinguish page listing from page content listing.

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?

It explicitly states when to call it: 'Use this to find a page_id before creating lead forms, boosting posts, or attaching a Page to an ad set's promoted_object.' It also gives a clear when-not condition ('This lists Pages, not their contents') and names the alternative photo-list tool.

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