publish_page_post

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

The description explains the core publish action and the scheduling behavior with time constraints. However, since no annotations are present, it does not disclose required permissions, side effects, or what happens when published defaults to true.

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, purposeful sentences with the action front-loaded and scheduling details neatly appended. No filler or redundant repetition of schema information.

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 a moderate 5-parameter surface, the description covers the main action and the non-obvious scheduling behavior. It omits permission requirements, but the tool is otherwise adequately scoped for an agent.

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%, and the description compensates by explaining the important published/scheduled_publish_time relationship and the 10-minute-to-6-month Unix timestamp range. The other parameters are self-explanatory from names and usage context.

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 is specific: 'Publie un message texte (ou avec lien) sur une Page Facebook' identifies the verb, resource, and target. It clearly distinguishes this tool from photo, carousel, and video publishing siblings.

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?

It gives clear scheduling guidance with published and scheduled_publish_time. It does not explicitly name alternatives or when not to use them, but the text/link scope makes the intended use reasonably clear.

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