ig_publish_carousel_from_files

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

With no annotations, the description carries the behavioral disclosure burden and does so well: it explains the two-step process of uploading each file as an unpublished Facebook Page media object via multipart upload, then reusing the CDN URL to build the carousel. This adds meaningful process transparency beyond the tool name.

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 efficient and front-loaded: the main purpose appears in the first sentence, followed by a concise explanation of the underlying mechanism. The additional detail about not needing external hosting earns its place and aids selection.

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?

The description covers the essential workflow and key operational detail, and an output schema exists so return values need no explanation. However, it omits prerequisites such as required Facebook/Instagram permissions, token scopes, or what happens if the linked page is not properly configured, which would matter for an agent invoking this publishing tool.

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. It clarifies that file_paths are local files and page_id is the linked Facebook Page used for the upload. However, it does not explain ig_user_id or caption beyond what their names imply, leaving part of the parameter semantics to inference.

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 ('Publie un carrousel Instagram') with a concrete resource scope ('2 à 10 images', 'depuis des fichiers locaux'). It clearly distinguishes itself from URL-based or page-only publish tools by emphasizing the local-file workflow and the Facebook Page upload mechanism.

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 conveys when to use this tool: when publishing Instagram carousels from local files, avoiding the need to host images elsewhere. It does not explicitly name sibling alternatives like ig_publish_carousel, but the context makes the intended use case clear.

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