create_page_post

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

With no annotations, the description carries the full behavioral disclosure burden. It discloses important traits: admin requirement, immediate vs. hidden publishing, and return format. It stops short of covering edge cases like conflicting parameters or idempotency, but it is substantially informative.

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 well-organized with labeled sections (Modes, Args, Requires, Returns). Every sentence adds value, and there is no fluff or repetition. It is concise yet complete for its complexity.

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 (6 params, no annotations) and the presence of an output schema, the description covers key behavioral aspects: modes, auth requirements, publishing behavior, and return value. It is sufficiently complete for an AI agent to invoke correctly.

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 description coverage is 0%, so the description compensates by explaining message, link, image_url, published, and access_token, including their roles across modes. It does not explicitly describe page_id, but the opening sentence implies its meaning. Overall, strong parameter guidance for a 0%-coverage 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 clearly states the tool's function with a specific verb and resource: 'Crea una publicación ORGÁNICA en la Página de Facebook'. It explicitly distinguishes from paid advertising ('NO es un anuncio pago'), which differentiates it from sibling ad-creation tools.

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 provides context on when to use the tool and when not to (not for paid ads), and explains that published=False creates a dark post for later promotion. However, it does not explicitly name alternative sibling tools, so it falls short of the highest bar for usage guidelines.

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