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

Annotations already establish readOnly=true, openWorld=true, and destructive=false, so the safety profile is clear. The description adds useful behavioral context about cross-workspace login reuse, current Page reporting, and conditional connect_url output, though it does not describe the page item shape in detail.

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 three compact sentences, front-loaded with the core list operation. Each sentence adds distinct value: scope, usage/alternative, and the no-login fallback.

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 one-parameter read-only list tool with no output schema, the description covers the key operational context: whose Pages are listed, which Page is current, how to switch, and what happens without a Facebook login. Nothing essential for correct invocation is 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?

Schema coverage is 100%, and the single workspace_id parameter is fully documented in the schema, including how to obtain it from list_workspaces. The description does not add parameter-specific meaning beyond the schema, so the baseline 3 applies.

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: it lists Facebook Pages the user can post to, plus the Page the current workspace posts as. It also distinguishes the tool from select_facebook_page, which is named as the follow-up action.

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 explicit when-to-use guidance: connecting Facebook to another workspace or switching Pages without a new sign-in. It routes the user to select_facebook_page for page selection and explains the no-login fallback via connect_url.

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