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

No annotations are provided, so the description carries the full disclosure burden. It only says 'Get recent posts'; it does not mention pagination behavior, date filtering semantics, the optional sentiment analysis and surcharge, or what the returned data looks like. This is a meaningful transparency gap for a tool with several options.

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 one clear, front-loaded sentence with no filler words. It is efficient and immediately communicates the core function, though it leaves out contextual details that are penalized in other dimensions.

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?

With five parameters, no output schema, no annotations, and a large family of sibling tools, this short description is not complete enough. It does not explain the result format, pagination limits, billing/surcharge behavior, or how to choose among the many related Facebook page content tools.

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 100% description coverage, so the parameters are already well explained. The description adds only the page ID context and does not provide additional semantic detail beyond what the schema supplies, so the baseline score of 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 states a specific action ('Get') on a specific resource ('recent posts from a Facebook page') keyed by page ID. This is clear enough to distinguish it from sibling tools for page details, photos, reels, videos, and comments, though it does not explicitly name alternatives like search_facebook_posts.

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 implies usage for retrieving posts from a known Facebook page ID, but it gives no explicit when-to-use or when-not-to-use guidance. There is no mention of how this compares to search_facebook_posts or to other content-specific page tools such as facebook_page_reels or facebook_page_videos.

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