Get Facebook Page Posts

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds the return format (list of posts with message, permalink, etc.), which is helpful but not substantially beyond annotations. No behavioral traits like auth requirements or rate limits are disclosed.

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 concise, well-structured with bullet points for parameters and return values, and front-loaded with purpose and prerequisite. Every 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?

Given the lack of output schema, the description provides a clear return type. It also covers prerequisites and pagination. For a read-only list tool with good annotations, this is adequately complete, though possible extra context like error handling is absent.

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 75% (missing limit description). The description adds value for limit (max, range, default) but misses the response_format parameter entirely. Overall, it provides some additional meaning but with a notable gap.

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 it lists posts from a Facebook Page feed. However, among many sibling tools like meta_get_post, meta_get_promotable_posts, etc., it doesn't differentiate itself, which limits clarity for tool selection.

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 a prerequisite (calling meta_list_pages first) and explains pagination, but it does not provide explicit guidance on when to use this tool versus other post-retrieval tools, nor does it state 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.