list_business_pages

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

Without annotations, the description must disclose behavioral traits. It only notes the env var requirement, failing to mention that the operation is read-only, safe, or whether it paginates. No details on rate limits, auth, or response behavior are provided.

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 two sentences: the first states the purpose, the second a key precondition. It is front-loaded, concise, and contains no extraneous 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?

The description is adequate for a simple list tool but lacks details about the return structure, pagination behavior, or error cases. Without an output schema, adding that context would improve completeness. Currently it meets minimum requirements.

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% (all parameters have descriptions in the schema). The description adds no additional meaning beyond what the schema already provides, such as format constraints or usage examples. Baseline 3 is appropriate.

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 states 'List Facebook Pages owned by the configured business,' which is a specific verb+resource pair. It distinguishes this tool from sibling list tools (e.g., list_ad_accounts, list_businesses) by specifying 'Facebook Pages' as the target entity.

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 mentions the requirement of META_BUSINESS_ID env var, implying the tool should only be used when that environment variable is set. However, it does not provide explicit guidance on when to use this tool versus alternatives, nor does it clarify limitations (e.g., only works for one business).

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