fb_schedule_post

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It usefully reveals the scheduling behavior and time restriction, but it does not mention expected results, side effects, prerequisites, or what happens if the publish_at constraint is violated.

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?

A single, front-loaded sentence conveys the core action, resource, and key time constraint with no redundancy. Every element earns its place.

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?

The description is adequate for a simple scheduling operation, but it lacks explicit routing away from immediate post creation and does not mention return values or failure modes. Given no output schema and no annotations, a slightly more complete description would include a sibling reference or expected result.

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 the baseline is 3. The description adds value by specifying the exact publish_at validity range ('10 minutes to 6 months out'), which the schema does not state. It does not add further detail about link, but the schema already documents all parameters adequately.

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 uses a specific verb ('Schedule') and resource ('a text post... on the Facebook Page'), with a clear temporal scope ('future time', '10 minutes to 6 months out'). This distinguishes it from immediate publishing siblings like fb_create_text_post.

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 scheduling use cases by specifying a future-time window, but it does not explicitly state that fb_create_text_post should be used for immediate publishing. An agent must infer the when-not-to-use boundary from the sibling names rather than from the description.

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