publish_reel

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

With no annotations provided, the description adds important behavioral context: asynchronous processing with polling up to 90 seconds, and the effect of share_to_feed. However, it does not cover permissions or rate limits.

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 three sentences with no redundant information. It starts with a clear main action followed by critical constraints and optional details, all front-loaded.

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 async nature, key parameter constraints, and optionality. It assumes the output schema explains return values. Missing explanations for 'account' and 'caption' parameters prevent full 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?

The schema has 0% description coverage, so the description must compensate. It explains video_url, share_to_feed, and cover_url but does not cover 'account' or 'caption'. This covers 3 of 5 parameters, providing partial but incomplete semantics.

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 explicitly states 'Publish a Reel', using a specific verb-resource combination. It further distinguishes from sibling tools like publish_image, publish_video, and publish_story by focusing on Reels and noting key constraints.

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 includes a prerequisite (video_url must be a public https URL) and explains the behavior of share_to_feed. While it does not explicitly name alternatives or when-not-to-use, the purpose clarity sufficiently differentiates it from siblings.

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