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

With no annotations, the description carries the full transparency burden. It discloses the sequence of operations (noise removal, silence cut, LUFS normalization, subtitle burn-in) and notes it is browser-based. However, it does not mention file handling, privacy, or output expectations, leaving some behavioral ambiguity.

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 a single, compact sentence that front-loads the entire processing pipeline. Every word contributes meaningful information, and the browser-based note adds relevant context without padding.

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?

Given the zero-parameter schema and lack of output schema, the description covers the essential purpose and processing steps. It could be more complete by specifying the input type (e.g., video file) or how the user triggers the '1 drop' interaction, but it is largely sufficient for a tool of this simplicity.

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?

The tool has 0 parameters, which earns a baseline of 4. The description provides no parameter-specific semantics because there are no parameters to describe; the schema is empty and fully covered.

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 specific action: 'ノイズ除去→無音カット→LUFS→字幕焼付を1ドロップで一気通貫処理', clearly listing the four processing stages. It distinguishes itself from the sibling tools (yt-denoise, yt-silence-cut, yt-lufs, yt-telop) by combining them into a single pipeline.

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 phrase '1ドロップで一気通貫処理' clearly implies the tool is for when you want all four processing steps done in one action. This gives context for use, though it does not explicitly mention when not to use it or compare against alternatives.

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