draft_video_script

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

With no annotations provided, the description carries the full burden. It only reveals that the tool is free, template-based, and requires no API key. It does not disclose whether it uses AI, the format of the output (full script or outline), or any constraints like length or language.

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?

Extremely concise at two sentences, with no wasted words. However, 'FREE' is front-loaded which may be slightly out of place for pure functional description, but it is not misleading.

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 no output schema and 2 parameters, the description lacks details about return value (script length, format), usage limitations, and how the template works. Sibling tools are present but no context on how this complements them.

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% with both parameters described. The description adds no extra meaning beyond what the schema provides (topic and hook_type). Baseline 3 is appropriate.

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 'Draft a TikTok video script' which is a specific verb+resource. It distinguishes from sibling tools (hashtag analysis, posting time optimization, trend search) by focusing on script creation. The mention of 'Template-based (no API key needed)' further clarifies the tool's nature.

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?

No guidance on when to use this tool vs alternatives. The description does not mention prerequisites, scenarios, or when not to use it. Sibling tools exist but no differentiation is provided.

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