create_video_creative

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

With no annotations, the description carries the full burden but only adds one behavioral detail: 'The API uses multipart file upload.' This is useful but incomplete; it does not disclose permissions, response behavior, or the notable mismatch that no file parameter appears in the input schema. The description is not misleading but has clear transparency gaps.

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 two short sentences with no filler. The main action is front-loaded, and the multipart note is a valuable addition that justifies its place. Every word earns its keep.

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 mutation tool with no annotations and no output schema, the description is too sparse. It does not explain what a video creative is, what creating it entails, how the group relates to media groups, or what the response contains. The multipart upload mention actually raises questions because the schema lacks a file parameter, leaving the agent without enough context to invoke the tool confidently.

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%, and each parameter (name, group, description) already has a clear description. The tool description adds no extra meaning to these parameters and does not compensate for the missing file parameter implied by the multipart note, though the baseline for high coverage is appropriately 3.

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 'Create a new video creative' with a specific verb and resource, distinguishing it from sibling tools like create_audio_creative or create_rich_media_creative. The mention of 'video' and the multipart upload detail further differentiate it from generic creative creation tools.

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 no guidance on when to use this tool versus alternatives like create_creative or create_rich_media_creative. It does not mention prerequisites, exclusions, or situations where another tool would be more appropriate, leaving the agent to rely solely on the tool name.

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