effect_scanlines

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

No annotations provided, so description must cover all behavioral traits. It mentions optional flicker but does not disclose whether the operation is destructive, permission requirements, or output format details beyond a dict.

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?

Two paragraphs: first line defines purpose, then concise Args list. Front-loaded, no fluff.

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 context of many sibling effects, the description adequately defines the effect and return value. Could mention limitations (e.g., codec support) but overall sufficient for a simple filter.

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?

Input schema has 0% description coverage, so description compensates by explaining each parameter with defaults and ranges (e.g., 'Pixels per scanline', 'Line opacity 0-1'). Adds meaning beyond schema types.

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 'Apply CRT-style scanlines overlay' with a specific verb and resource. It distinguishes from sibling effects like chromatic_aberration or glow by focusing on the CRT monitor scanline effect.

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 explicit guidance on when to use scanlines over other effects. The description implies use for CRT-like aesthetics, but does not contrast with siblings or mention prerequisites.

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