List Scheduled Posts

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

Beyond the annotations (readOnlyHint, destructiveHint), the description discloses the UTC/Page-local time behavior and, crucially, that Reel availability in the queue is UNVERIFIED against the live API. The explicit assertion that an empty or Reel-less result is not evidence against a scheduled Reel prevents a likely misinterpretation.

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 core action is front-loaded, followed by practical use cases and a necessary caveat. Each sentence earns its place, though the Reels caveat is somewhat verbose.

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?

Even with no output schema, the description conveys the essential return value (scheduled posts with publish times and accessible post_id), the read-only safety, and the Reel limitation. Pagination is documented in the schema. It could explicitly list all returned fields, but nothing critical is missing for correct invocation.

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% for all 4 parameters, and the tool description does not add parameter-level semantics beyond what the schema already provides. The baseline of 3 applies appropriately.

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 ('List'), the exact resource ('Page posts that are queued to publish later'), and a distinctive output detail (publish time echoed in UTC and Page-local time). It clearly differentiates from sibling list tools by using 'scheduled' and 'queued to publish later'.

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?

It explicitly says this tool is the read-only way to get the post_id for facebook_update_post or facebook_delete_post, and warns about Reel invisibility so agents don't misuse empty results. It stops short of comparing with facebook_list_posts/facebook_list_reels or stating when not to use it, so it doesn't earn a 5.

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