Create Facebook Page Post

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

Annotations are minimal (readOnlyHint=false implies mutation) and the description carries the burden, delivering meaningful context: the publish-vs-draft behavior, the ~63,206 character limit, the 10-min-to-30-day scheduling window, and the Page Publishing Authorization requirement for scheduling. No contradiction with annotations; description's 'Creates a new post' aligns with readOnlyHint=false.

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?

Well-organized with purpose, prerequisite, Args, Returns, and Notes sections — front-loaded with the core intent before details. The Args list partially restates the schema, which is mildly redundant, but each entry earns its place by adding constraints (scheduling window, link preview) not present in the structured fields.

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 6 parameters, no output schema, and no annotations covering the behavior, the description covers the essentials: return value (Post ID), prerequisite call, constraints on scheduling, and length limits. Minor omission is unprompted error-case handling, but for a create-post tool this is sufficiently complete.

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 coverage is 100%, so the baseline is 3. The description adds valuable nuance beyond the schema: link 'creates a link preview', published defaulting to true with draft semantics, and scheduled_publish_time must be 10 min to 30 days out with published=false. This materially helps an agent use parameters correctly beyond the bare schema descriptions.

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?

States the verb 'creates' with a specific resource ('a new post on a Facebook Page'). The sibling tools meta_create_photo_post, meta_create_video_post, and meta_create_live_video make it clear this is the general text-post variant, so an agent can distinguish it without opening schemas.

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?

Provides a clear prerequisite ('meta_list_pages must be called first to load page tokens') and a follow-up routing if the user wants photos or videos would be handled by named siblings. However, it never explicitly says when NOT to use this tool or points to alternatives like meta_create_photo_post or meta_create_video_post, leaving the choice between post types implied rather than stated.

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