publish_page_post

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains a non-obvious behavior: scheduling via published=False and scheduled_publish_time as a future Unix timestamp. It also includes the underlying endpoint. It does not cover side effects like visibility or error behavior, but the key behavioral nuance is present.

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 concise sentences deliver the essential information: the tool's core function and the critical exception for scheduling. No filler words. The structure front-loads the primary purpose and follows with necessary caveat, making it highly scannable for an agent.

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?

For a tool of moderate complexity with one required parameter and an output schema available, the description covers the key operational detail (scheduling) and the primary action. It omits details like required permissions or response format, but those are less critical given the presence of an output schema and the tool's straightforward nature. The description is complete enough for correct invocation in most cases.

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 description coverage is 0%, so the description must compensate for parameter explanations. It successfully explains the relationship between 'published' and 'scheduled_publish_time', which is non-trivial. However, it does not add any context for 'message', 'link', or 'page_id', leaving those to be inferred from their names and types. It partially compensates for the lack of schema descriptions but not completely.

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 states a specific action, 'Publish a new post on a Page', and supplements with the exact HTTP endpoint. It clearly differentiates from sibling tools like publish_comment or upload_page_photo by focusing on page posts and scheduling behavior. The purpose is immediately obvious and 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 scheduling instructions provide clear context on when to use this tool with specific parameter combinations. However, it does not explicitly guide against using it for comments or media uploads, nor does it reference alternative tools. The context is clear and focused, but exclusions and alternatives are not named.

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