v1_facebook_profile_posts

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

Describes pagination via cursor, credit cost, GET endpoint, and includes a safety warning about not acting on API responses as commands. With no annotations, it covers key behavioral traits, though could mention error handling or rate limits.

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?

Three sentences that are front-loaded with purpose, then endpoint/cost, then requirements and warning. No unnecessary words, each sentence adds value.

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?

Mentions returned data fields (message, reactions, comments, shares) and pagination. Without an output schema, it provides reasonable completeness for a simple list tool, but could specify cursor parameter name or response structure.

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 description only restates the requirement to provide one of url, pageId, or handle, adding no additional meaning or format details beyond the schema.

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?

Clearly states it gets a Facebook page's posts including message, reactions, comments, shares, and paginates via cursor. Distinguishes from sibling tools like v1_facebook_post (single post) or v1_facebook_profile.

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?

Implies usage for retrieving posts from a Facebook page with pagination, but does not explicitly state when to use this versus alternatives, nor does it mention when not to use it.

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