Facebook Group Posts

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

Annotations say readOnlyHint=false, which is unusual for a 'fetch' operation, and the description addresses this directly with 'Read-like POST requests do not publish to social platforms', explaining the apparent mutation. It also discloses the paid-credit consumption and the 3-post-per-page API limit, which are valuable behavioral traits beyond the annotations. However, it does not say whether pagination stops, when the cursor is exhausted, or what the failure mode is if confirm is omitted.

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 short sentences, front-loaded with the core purpose and scope. One sentence ('Potentially consumes paid API credits; requires confirm=true; Read-like POST requests do not publish to social platforms') packs three distinct facts but reads as a run-on list and could be split.

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 6-param, no-output-schema, credit-consuming tool, the description covers the important gaps: the API's 3-post limit, credit cost, the confirm flag, the return fields, and the read-like POST behavior. It omits error handling and cursor exhaustion behavior, but the essentials an agent needs to invoke safely are present.

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 all six parameters are already documented in the schema. The description reinforces the sort_by enum values (TOP_POSTS, RECENT_ACTIVITY, CHRONOLOGICAL, CHRONOLOGICAL_LISTINGS) and the confirm requirement, but adds no format or syntax detail beyond the schema. 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?

Starts with a specific verb+resource: 'Fetches posts from a public Facebook group', and clearly distinguishes it from the similarly-named sibling facebook_facebook_group_info by stating it returns post data. An agent can tell what it does immediately.

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?

Mentions the constraint 'limited to 3 posts per page', the paid-credit cost, and the confirm=true requirement, but does not name when to use this versus facebook_facebook_group_info or facebook_facebook_group_posts alternatives. The confirm requirement is a strong usage signal, but there is no explicit when-not-to-use guidance.

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