meta_list_pages

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It states the tool lists pages but does not mention whether it reads actual API data, if it requires specific permissions (e.g., pages_read_engagement), rate limits, or any side effects. The description is insufficient for an agent to understand behavior beyond the basic action.

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, well-structured sentence that front-loads the key information: the tool lists pages and returns specific fields. No unnecessary words, making it highly concise.

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 parameterless list tool, the description covers the main purpose and returned fields. However, it lacks details on pagination, result limits, or whether the list is comprehensive. Given no output schema, slightly more context (e.g., 'returns up to 100 pages') would improve completeness.

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 has zero parameters, so there is nothing to document. The description adds meaning by clarifying that the tool retrieves pages managed by the token, effectively explaining the implicit context. Since schema coverage is 100% (empty), the description compensates well by describing the tool's scope.

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', the resource 'Facebook Pages the token manages', and explicitly lists the returned fields (id, name, category, fans). It differentiates from sibling tools like meta_list_ad_accounts or meta_list_campaigns by specifying pages specifically.

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 explicit guidance on when to use this tool versus alternatives. The phrase 'the token manages' implicitly suggests authorization requirements, but there is no mention of prerequisites, preferred scenarios, or when not to use it. Sibling tools cover similar list operations, making this omission a gap.

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