Create Post

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

The description goes beyond the annotations (idempotentHint: false, destructiveHint: true) by disclosing that it validates text, checks posting limits, publishes via the web composer, and returns a clear error if cookie-based writing is decommissioned. This provides valuable behavioral context without contradicting the annotations.

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 three sentences, starts with the core purpose, then explains the process and failure handling. Every sentence earns its place with no repetition of schema information, making it appropriately concise and front-loaded.

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 three fully documented parameters, an output schema present, and annotations for idempotency/destructiveness, the description adds sufficient context: it explains the publishing mechanism, validation, and error behavior. No critical information is missing for a tool of this complexity.

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 covers all parameters (coverage 100%) and already describes 'status', 'confirm', and 'account_id'. The description adds context for account_id (active vs specified identity) and mentions validation of text, but does not add syntax or format details beyond the schema, so it stays at baseline 3.

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 the verb 'Publish' and the resource 'a text post', distinguishing it from sibling tools like create_photo_post and create_video_post. It also specifies the identity context ('active or specified Facebook identity'), making the purpose 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 clearly implies this tool is for text posts only, which differentiates it from photo/video/carousel creation siblings. However, it does not explicitly name alternatives or state when not to use this tool, so it stops short of full exclusion guidance.

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