publish_carousel

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

With no annotations, the description carries full burden. It mentions media must be publicly accessible URLs, which is useful context, but lacks critical behavioral details: whether this is a write operation (implied by 'Publish'), authentication needs, rate limits, error handling, or what happens on success (e.g., returns a post ID).

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 a single, efficient sentence that front-loads the core purpose and key constraint (2-10 items, public URLs). Every word earns its place with no redundancy or fluff.

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 write operation tool with no annotations and no output schema, the description is incomplete. It misses essential context: what the tool returns, error conditions, side effects, and how it differs behaviorally from sibling publishing tools, leaving gaps for an agent to use it correctly.

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%, so the schema fully documents parameters. The description adds minimal value beyond schema: it reiterates the 2-10 range for image_urls and specifies 'images or videos', but doesn't clarify format requirements or caption usage beyond what's in schema descriptions.

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 ('Publish') and resource ('a carousel (album) post'), specifying it's for 2-10 images or videos. It distinguishes from siblings like publish_media or publish_reel by focusing on multi-media albums, but doesn't explicitly contrast them.

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 when posting multiple media items (2-10) as a carousel, but provides no explicit guidance on when to choose this over publish_media or publish_reel, nor any prerequisites or exclusions beyond URL accessibility.

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