threads_create_video_post

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the action ('create and publish') without covering potential side effects, authorization requirements, rate limits, or the nature of the returned result. The inclusion of 'ctx' as a parameter is also not part of the actual schema, adding minor confusion.

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 relatively concise with one main sentence and a short argument list. However, the 'Args' block largely duplicates schema information and could be trimmed, but it does not harm usability significantly.

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 tool has an output schema, so return values do not need explanation. However, the description lacks usage guidance and behavioral transparency, though the parameter explanations are sufficient for basic invocation. It is minimally viable but has clear gaps.

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, and the description compensates by explaining each parameter: video_url as the URL, text as optional content, and reply_control with its enum values. This adds needed meaning beyond the bare schema types.

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 states a specific verb+resource: 'Create and publish a post with a video to Threads.' It clearly distinguishes from sibling tools like threads_create_post and threads_create_image_post by specifying the video medium.

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 video posts but does not explicitly compare to alternatives or state when not to use this tool. It provides the required video_url parameter but lacks exclusions or explicit guidance versus sibling tools.

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