Publish Facebook Page Story

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

Annotations already signal a non-read-only, non-idempotent write with no destructive hint. The description adds useful context beyond this by stating the meta_list_pages prerequisite and the success return value (story ID), though it does not cover rate limits or failure modes.

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 and front-loaded with the action, followed by the prerequisite, args, and return value in a clear structure. The Args bullets are somewhat redundant with the schema but not excessive.

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 simple publish tool with no output schema, the description provides the essential return value and a critical prerequisite, while the schema covers parameter details. It does not discuss error conditions or media accessibility, but nothing critical is missing for successful 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?

The input schema has 100% description coverage for all four parameters, so the baseline is 3. The description's Args section mostly restates schema descriptions and omits the response_format parameter, adding no new semantic detail beyond the schema.

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 'Publishes a story (photo or video) to a Facebook Page,' which gives a specific verb, resource, and media type. This clearly distinguishes it from sibling tools like meta_create_post or meta_publish_page_reel by scoping it to Page stories.

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 includes an explicit prerequisite: 'Requires: meta_list_pages called first to load page tokens,' which is actionable guidance for correct invocation. However, it does not explicitly compare against alternative publishing tools or state when not to use this tool.

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