create_cardnews_batch

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

Describes creation behavior: one card per file plus optional merged card. No annotations provided, but lacks disclosure of side effects, error handling, file requirements, or output specifics.

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?

Single sentence with essential information, no filler. Front-loaded with main action and conditional combine behavior.

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?

Core logic is clear, but missing details on output directory and model parameters. No output schema or error handling info. Adequate but not comprehensive for a 5-param batch operation.

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?

Description reinforces combine parameter's effect. With 60% schema coverage, some parameters (outputDir, model) remain undocumented. Description adds marginal value beyond schema for filePaths and folder.

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?

States clear verb '생성한다' (creates) and resource '여러 자막 파일을 회차별 카드' (multiple subtitle files into episode cards). Distinguishes from sibling tools that handle single file or text input.

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?

Implies batch usage for multiple subtitle files, but no explicit guidance on when to use or not use versus alternatives. No when-not-to-use or prerequisite conditions mentioned.

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