Post to Facebook, Instagram or Threads

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

Annotations indicate a write operation (readOnlyHint=false). The description adds important context: it publishes immediately, requires user confirmation, and needs a connected Meta account with posting permission.

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 relatively long but well-structured, front-loading the primary purpose. Some redundancy exists (e.g., repeating 'connected'), but it remains clear and informative.

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?

Given the tool's complexity (multiple platforms, media types, connection requirements), the description covers essential aspects. The output schema is not shown but is mentioned (has output schema: true), so the description is adequate.

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%, providing a baseline of 3. The description adds meaning by explaining the `target` enum values, the types of URLs accepted for `imageUrl`/`videoUrl`, and the need to call `upload_file` for local files.

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 ('Publish') and resource ('Facebook Page, its linked Instagram, OR the brand’s Threads account'), clearly distinguishing from sibling tools like manage_meta_post (editing) and create_meta_ad (ad creation).

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 explains when to use the tool (publishing to connected accounts) and includes a caution ('confirm copy + media first') but does not explicitly mention when not to use or list direct alternatives for specific scenarios like editing a post.

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