Video Oluştur

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

Discloses key behaviors: background processing, rate limit (200 req/min), file format/size/duration constraints, single active video rule, approval requirement, auto-removal of old videos. No annotations provided, so description fully carries the burden.

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?

Compact yet comprehensive: 4 sentences efficiently cover purpose, constraints, and behavior. No redundancy. Each sentence adds essential 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?

For a creation tool with 5 parameters and no output schema, the description covers all behavioral aspects: processing, limits, approval workflow, auto-removal, and references sibling tool for status. Complete and actionable.

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 coverage is 100%, but description adds significant value: file format/size/duration constraints not in schema, explains default for videoContentType, and clarifies productContentIds limit. Goes well beyond schema descriptions.

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?

Clearly states it creates video for product content, downloading from URL and processing in background. Distinguishes from sibling tools like trendyol_get_videos which are for retrieval.

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?

Explicitly mentions tracking status with trendyol_get_videos, and provides constraints (1 active video per productContentId, max 100 linked IDs) that guide appropriate usage. Clear context for when to use this tool.

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