Create Facebook Photo Post

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

Annotations provide no safety hints (all false), so the description must disclose side effects. It only states 'Publishes a photo post' and lists parameters; it does not address permissions, idempotency, error conditions, or the impact of 'published' being false. This is a significant gap for a mutation operation.

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 two sentences plus a compact argument list, front-loaded with the main action and no redundant text. Every line adds necessary context, making it appropriately concise.

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 tool has no output schema and a moderate parameter set, so the description should clarify return behavior and edge cases. It does not explain what the response_format parameter does or how results are returned, nor does it cover the semantics of 'published: false' (e.g., draft vs. scheduled). These gaps leave an agent uncertain about the full API contract.

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 schema has only 40% description coverage, and the description adds useful clarifications: it defines 'url' as 'Public URL of the image', 'caption' as 'Photo caption/message', and notes 'published' defaults to true. However, it omits the 'response_format' parameter entirely, leaving the agent unaware of this option and its enum values.

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 clearly states 'Publishes a photo post to a Facebook Page,' which is specific and distinct from siblings like meta_create_video_post or meta_create_live_video. It names the action and resource precisely, making it unambiguous.

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 from the tool name and the phrase 'photo post' that it is for photo publishing, but it does not explicitly mention alternatives or when not to use it. There is no guidance on selecting this over video or live-video tools, though an agent can infer from the sibling list.

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