download_carousel

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

No annotations are provided, so the description carries the full burden. It discloses that it returns an array of media URLs in original slide order at native aspect ratio. However, it does not mention potential limitations (e.g., rate limits, authentication) or behavior if the URL is not a carousel.

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 two sentences, front-loading the action and key details. Every sentence adds value without redundancy.

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 the simple tool (1 parameter, no output schema), the description is complete. It explains what the tool does, the input requirements (public carousel post), and the output format (array of URLs in order).

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 100% schema coverage, the baseline is 3. The description adds little beyond the schema's parameter description, as both specify the URL must be a public Instagram carousel post. The description does not provide additional semantic details like URL format expectations.

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 specifies that it downloads every slide of a public Instagram carousel post, including both photos and videos. It distinguishes itself from sibling tools like download_video (single video) and download_reels (reels) by focusing on carousel posts.

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 for public carousel posts but does not explicitly state when not to use it or mention alternative tools. The context of sibling tools provides some guidance, but the description lacks explicit when-to-use/when-not-to-use instructions.

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