publish_page_carousel

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

The description discloses a non-obvious implementation detail: images are first uploaded unpublished, then attached to the post. With no annotations, this is helpful behavioral context. However, it does not mention that the post becomes publicly visible, what permissions are needed, or how failures are handled.

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 with no filler. The main purpose is front-loaded, and the second sentence adds meaningful process detail without over-explaining.

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 mutating publishing tool with no annotations and zero schema descriptions, the description is too thin. It lacks usage guidance, parameter semantics, and behavioral consequences. The process note is useful but does not sufficiently equip an agent to invoke the tool correctly among many similar siblings.

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 must compensate for documenting parameters. It mentions images and 'post' vaguely, but never defines `message`, `page_id`, or the exact role of `image_urls`. It adds little beyond what the parameter names themselves already imply.

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 action ('Publie') and the resource ('un carrousel sur une Page Facebook'), and the parenthetical '(plusieurs photos)' disambiguishes it from simple photo or text posts. However, it does not explicitly differentiate this URL-based carousel from the sibling `publish_page_carousel_from_files`.

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?

No guidance is provided about when to choose this tool over alternatives such as `publish_page_carousel_from_files` or `publish_page_photo`. The only hint is the schema's `image_urls` field, but the description itself never states conditions or exclusions.

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