Create Post

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the agent knows this is a non-destructive external write. The description adds that publishing can be deferred rather than immediate, but says nothing about permission requirements, failure modes, or rate limiting for a mutation tool. An output schema exists, so return values need not be explained.

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?

Two short sentences, front-loaded with the action and content type, second sentence carrying the one hard requirement. Zero waste and nothing to trim.

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?

With an output schema present and annotations covering the safety profile, the description supplies the key gap: the message/link requirement and the immediate-vs-scheduled fork. Minor omissions remain around Page selection and scheduling prerequisites, though the schema descriptions cover both.

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 50%: page and scheduled_time are fully documented in-schema, while message and link carry no schema description at all. The description partially compensates by stating at least one of message/link is required, but adds no format, length, or content-type guidance beyond that constraint.

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?

Specific verb+resource: 'Publish (or schedule) a text/link post on a Page' tells an agent exactly what is produced and the content type, which implicitly separates it from create_photo_post and create_reel among the siblings. It stops short of naming those alternatives, so differentiation requires inference.

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?

'Needs a message, a link, or both' gives a clear precondition for calling. The '(or schedule)' parenthetical implies when to use scheduled_time, but no alternative tool is named and no explicit when-not guidance is given.

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