pages_publish_post

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

No annotations exist, so the description must carry the full burden. It discloses scheduling behavior (if scheduled_publish_time set, post is scheduled and published=False), but it omits other behavioral aspects like the effect of confirm, permission requirements, side effects, or reversibility. The overall behavioral disclosure is minimal.

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 concise and front-loaded, with the primary action stated first and the parameter note appended efficiently. It earns its place without fluff, though it omits important details that would make it more useful.

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 six parameters, no output schema, and no annotations, the description is incomplete. It does not cover the confirm parameter, expected return value, or full behavior of published/scheduled_publish_time interplay. The tool's complexity warrants a more thorough description.

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?

With 0% schema description coverage, the description must compensate, but it only explains scheduled_publish_time and its relationship with published. Other parameters (page_id, message, link, confirm) receive no semantic explanation, leaving the agent to infer their meaning from names alone.

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 publishes a 'text/link post to a Page,' which is a specific action and distinguishes it from sibling tools like pages_publish_photo. The verb 'publish' and resource 'Page' are explicit, 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 implies usage by specifying 'text/link post' rather than photo, suggesting when to use this tool over pages_publish_photo. However, it lacks explicit alternatives, exclusions, or context such as prerequisites or conditions for use.

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