Publish Facebook Page Story

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

Annotations provide no hints (readOnlyHint=false, destructiveHint=false). Description states it publishes a story (write operation) and returns the story ID. Lacks details on potential side effects, limitations, or when the story appears.

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?

Short and to the point with a clear list of parameters. The prerequisite is clearly stated. Could be slightly more structured but overall efficient.

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?

Covers basic purpose, prerequisite, and return value. However, for a mutation tool with no output schema and many similar siblings, more context about use cases or differences would improve completeness.

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 schema already describes parameters. Description repeats some (page_id, media_url, media_type) but adds minimal extra meaning (e.g., 'Public URL'). The response_format parameter is not mentioned in description.

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?

Clearly states it publishes a story (photo or video) to a Facebook Page. The verb 'publishes' and resource 'story' are specific. However, it does not explicitly distinguish from sibling tools like meta_create_photo_post or meta_publish_page_reel.

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 a prerequisite (meta_list_pages to load page tokens) which helps usage. But no guidance on when to use this tool versus alternatives like meta_create_photo_post (for feed posts) or meta_publish_page_reel.

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