Publish Video Thread

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

Annotations provide no behavioral hints, so the description carries full burden. It discloses that video processing may take time and that the tool polls for up to 60 seconds, which is valuable. However, it does not describe the return value or state after polling.

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 extremely concise, using only four lines to convey purpose, arguments, and a behavioral note. Every sentence is necessary and front-loaded with the most important information.

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 6 parameters, no output schema, and moderate complexity. The description covers core functionality and the polling timeout, but lacks details on return values, how to handle polling results, and leaves three parameters undocumented. It is adequate but not fully complete.

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 only covers 3 of 6 parameters (threads_user_id, video_url, text), omitting reply_control, location_id, and response_format. It adds no additional meaning beyond the schema, which already describes those omitted parameters. Schema coverage is 67%, so baseline is 3, but omission reduces score.

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 'Publishes a video post to Threads,' specifying the verb (Publishes), resource (video post), and platform (Threads). This distinguishes it from sibling tools like threads_publish_image or threads_publish_text.

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 lists required arguments and includes a note about video processing time, but does not explicitly guide when to use this tool versus alternatives or mention prerequisites. The note about polling is helpful but not a full usage guideline.

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