List Facebook Pages

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

The description adds significant behavioral context beyond annotations: it reveals that the tool caches page access tokens for subsequent calls and that tokens are managed automatically. The annotations (readOnlyHint, idempotentHint, destructiveHint false) already cover safety, and the description enriches with workflow-relevant details.

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 well-organized: a clear purpose statement, an important usage note in bold, a concise list of return fields, and a helpful tip. No redundant sentences; every part earns its place, and the critical 'call first' note is front-loaded.

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?

With no output schema, the description provides a detailed list of return fields, including the nested instagram_business_account.id. It also explains the caching behavior and the need to call it first, covering all essential aspects an agent needs to invoke it correctly. No missing critical information.

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 single parameter response_format is fully documented in the schema (coverage 100%), including its enum and default. The description does not add any extra explanation about the parameter, so it relies on the schema. Baseline 3 is appropriate since the schema already handles it.

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 'Lists all Facebook Pages managed by the authenticated user,' using a specific verb and resource. It distinguishes itself from siblings like meta_get_page (single page) and meta_list_instagram_accounts (Instagram accounts) by explicitly covering all pages and linking to subsequent operations.

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 instructs 'Call this tool first before any page or Instagram operations' and explains that it caches access tokens, which is crucial guidance for sequencing. It also clarifies that token management is automatic, leaving no ambiguity about when and how to use it.

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