Publish a clip to social platforms

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal important behavior: TikTok posts land as drafts, Instagram and YouTube publish directly, and scheduling is optional. However, it does not disclose potential side effects (e.g., irreversible actions, rate limits, error handling) or the response format, leaving gaps for a mutating operation.

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, front-loaded with the core action and then providing crucial details about platform behavior, requirements, and scheduling. Every sentence adds value without 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 tool with 7 parameters and no output schema, the description is only partially complete. It covers prerequisites and scheduling but omits details on how parameters like job_id and clip_index are used, what happens after posting (return values), and potential error conditions. The description provides a good starting point but leaves an agent guessing on several operational aspects.

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 only 14% (only scheduled_date has a schema description). The description adds context for scheduled_date (ISO-8601) and mentions platforms implicitly, but fails to explain job_id, clip_index, title, description, timezone, or how they relate to the publishing process. Given the low schema coverage, the description should have compensated with parameter explanations but did not.

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 tool's purpose: posting one clip to connected social accounts. It specifies the resource (clip) and action (post), and distinguishes from siblings by focusing on publication rather than processing, listing, or quota operations. The platform-specific behavior (TikTok draft vs direct) adds clarity.

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 provides clear prerequisites (connected social profile or Upload-Post key) and mentions optional scheduling, which helps the agent decide when to use it. However, it does not explicitly state when not to use this tool or compare it to alternatives like process_video or recut_clip, though the name and purpose make the context obvious.

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