List Pages

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

Beyond the annotations, the description discloses important behavioral traits: it reads exactly one window of up to 100 Pages, does not follow a cursor, and never returns Page access tokens. It also explains how to interpret hasMore, which is crucial for avoiding false conclusions about missing Pages.

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 front-loaded with the core purpose, then adds two high-value caveats about token privacy and incomplete pagination. Every sentence earns its place and no wording is wasted.

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 zero-parameter, read-only listing tool with no output schema, the description supplies enough return-field detail and a critical pagination warning. It gives the agent everything needed to call the tool and avoid misreporting a Page as missing.

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 tool takes zero input parameters, so there is no parameter semantics to clarify. The description appropriately focuses on return behavior and pagination constraints instead.

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 states a specific verb and resource: list the Facebook Pages the operator administers via /me/accounts. It also names the returned fields (id, name, category, granted tasks, token availability), making it clearly distinguishable from single-Page tools like facebook_get_page.

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 gives clear operational guidance for using the result: hasMore true means the list is incomplete, so a missing Page may still exist and should be addressed by raw Page ID. It does not explicitly name alternative tools such as facebook_get_page or facebook_whoami, so it stops short of full when-to-use/when-not guidance.

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