Publish Carousel Thread

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

Describes the three-step flow (create item containers, create carousel container, publish), which adds valuable context beyond the schema and annotations. However, it does not disclose side effects, authentication, or potential errors. Annotations are all false, so description carries the full burden.

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?

Extremely concise (90 words) with a clear structure: purpose sentence, flow step list, parameter listing. No redundant information, all sentences earn their place.

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?

Covers the main procedure and key parameters, but lacks information on return values (no output schema), error handling, or prerequisites (e.g., URL accessibility). For a multi-step mutation tool, this is a gap.

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 description lists 'threads_user_id', 'items' (with url and type details), and 'text' (optional), covering 3 of 5 parameters. Schema coverage is 40% (2 params described), so description compensates somewhat but misses 'reply_control' and 'response_format'. Adds meaning for 'items' but not for others.

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?

Clearly states it publishes a carousel post (2–20 images/videos) to Threads, which differentiates it from sibling tools like threads_publish_image and threads_publish_video. The verb 'Publishes' and resource 'carousel post' are specific.

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?

Implicitly tells when to use (for carousel with 2-20 items), but does not explicitly contrast with alternatives like publishing a single image/video. No when-not or prerequisite conditions are given.

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