List Facebook pages

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

Annotations already declare readOnlyHint=true, making the non-destructive nature clear. The description adds minimal context ('connected to a profile') but does not discuss pagination, limits, or authentication scoping. With annotations covering safety, this is adequate but adds little new behavioral insight.

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 sentence with no unnecessary words. It is front-loaded and perfectly concise for the minimal information it conveys. While some might argue it's too brief, conciseness is valued, and it earns full marks here.

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?

Given the presence of an output schema, the description does not need to explain return values. However, the minimal description does not clarify parameter usage or provide enough context about the scope of 'Facebook pages' (e.g., owned, managed, or accessible). It is minimally adequate but not robust.

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 one parameter ('profile') with 0% description coverage. The description implies that the parameter determines which profile's pages are listed, but it does not clarify if it's required, what values are accepted (e.g., ID or name), or whether omitting it defaults to the authenticated user's profile. This is insufficient for optimal agent invocation.

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 indicates the tool lists Facebook pages associated with a profile, distinguishing it from similar platform-specific tools like get_linkedin_pages. However, it does not specify whether it refers to the authenticated user's own pages or pages the user manages, leaving slight ambiguity.

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 guidance is provided on when to use this tool versus alternatives or when not to use it. Among many sibling 'get_' tools for different platforms, there is no contextual advice, leaving the agent to infer without support.

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