list_business_pages

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

With no annotations provided, the description carries the burden of disclosing behavior. It mentions the env var requirement and implicitly indicates a read-only operation ('List'), but it does not describe pagination behavior, default fields, or any other side effects or constraints beyond the env var. Adequate basic disclosure but lacks depth.

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, front-loaded sentence that states the action, resource, scope, and a critical prerequisite. Every word earns its place, with no filler or repetition of schema information.

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 simple list tool with no output schema and clear parameter documentation, the description is mostly complete. It covers purpose and a key environmental requirement. However, it does not mention pagination or what fields are returned by default, which would be marginally helpful but not essential given the schema and simple nature of the tool.

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 description coverage is 100%, so the parameters (after, limit, fields) are already well-documented. The description adds no additional parameter-specific semantics beyond the env var requirement, which is not a parameter. Baseline 3 is appropriate given the schema handles the details.

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 contains a specific verb ('List') and resource ('Facebook Pages') with a clear ownership scope ('owned by the configured business'), distinguishing it from sibling tools like list_businesses or list_business_ad_accounts. It is immediately obvious what this tool does.

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 clearly indicates the tool is for listing Facebook Pages associated with the configured business, which establishes when to use it. It also notes the required META_BUSINESS_ID environment variable, a useful prerequisite. However, it does not explicitly mention when not to use it or name alternative tools for similar operations.

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