Create video brief

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

Beyond annotations (which are all false), the description discloses asynchronous behavior ('rendering continues asynchronously'), timing ('typically a few minutes'), the immediate return of job and run IDs, and the polling pattern. It also notes write-scope requirement, adding meaningful context.

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?

Three sentences: purpose, async behavior/polling, and auth/alternative. Each sentence carries essential information 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 complex tool with 15 parameters and no output schema, the description covers invocation (purpose, required scope), expected immediate returns (job/run IDs), and follow-up (polling status). It gives a complete mental model 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 each parameter. The description adds general context about a 'structured brief' but no parameter-specific details, which is acceptable given the baseline.

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 clear action: 'Create a new video job from a structured brief and trigger the render pipeline.' This uses a specific verb and resource, and differentiates from siblings by explicitly naming edit_video_brief for modifying existing jobs.

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?

It provides explicit when-to-use ('Create a new video job'), when-not-to-use ('To change an existing job, use edit_video_brief instead of creating a duplicate'), and follow-up guidance ('poll get_job_status until draft_ready'). It also states the auth requirement ('key with write scope').

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