threads_publish_carousel

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

Adds context beyond annotations: cross-share failure behavior, geo-gating eligibility, location permission requirement, reply control defaults. Annotations are minimal, so description provides useful behavioral insights.

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 sentences, front-loaded with core purpose, then lists key features. No filler, every word contributes.

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 core functionality well but lacks details on return values or the container-based publishing process (implied by sibling threads_get_container_status). For an 8-param tool with no output schema, a brief note on response structure would improve completeness.

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 100%, but description adds synthesized value: explains cross-share, geo-gating, location tagging at a high level, plus detail on allowlisted_country_codes normalization and creator visibility. Goes beyond bare schema.

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?

Description clearly states 'Publish a carousel post on Threads with 2-20 images/videos', specifying verb, resource, and constraints. Distinguishes from sibling tools like threads_publish_image or threads_publish_video by focusing on multiple media items.

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?

Implies usage for carousel posts via the description. Context is clear relative to siblings, but no explicit when-not-to-use or alternatives beyond the parameter notes (e.g., location_id parent container only).

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