list_pages

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

No annotations are provided, so the description carries the behavioral burden. 'Liste' clearly signals a read-only listing operation, and the description reveals that result entries include id, nom, and abonnés. It does not mention pagination or rate limits, but for a zero-parameter read tool the essential behavior is well conveyed.

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 a single concise sentence in French with no filler and the key scope information ('accessible avec ce token') and output fields are front-loaded. Every word contributes to the definition.

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?

The description is sufficiently complete for a zero-parameter read-only listing tool: it says what is listed, under what token scope, and what fields are returned. The output schema likely covers the exact return shape, so explained return details are not required; only pagination or limit behavior could be additionally useful but is not a major gap.

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 is empty, so there are no parameter semantics to document. The description adds no parameter-level details, but the baseline for a zero-parameter tool is 4.

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 uses a specific verb ('Liste') and a specific resource ('Pages Facebook accessibles avec ce token'), and states the returned fields (id, nom, abonnés). This clearly distinguishes it from sibling tools like get_page or list_page_posts.

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 phrase 'accessibles avec ce token' implies the tool should be used when the agent needs the set of Facebook Pages available to the current token. However, it does not explicitly state when to prefer this over alternatives such as get_page or list_page_posts.

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