effect_chromatic_aberration

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

No annotations provided, so description carries full burden. It explains the effect (RGB split) and parameters, but does not disclose side effects, prerequisites, or file requirements. Adequate but could be more detailed.

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?

Concise with a clear intro, Args section, and Returns. Every sentence adds value. No wasted words.

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?

Covers purpose, parameters, and return value. For a simple video effect, this is near complete. Could mention input video existence or that it's an effect applied to video, but not critical.

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?

Adds meaningful descriptions for all 4 parameters beyond the schema, which only has names and defaults. Describes intensity as 'Pixel offset amount', angle as 'Separation direction'. Also explains return value.

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 'Apply chromatic aberration - RGB channel separation' with a specific verb and resource. Mentions it's a trendy RGB split effect for glitch aesthetics, but does not explicitly distinguish from similar sibling tools like glitch_rgb_shift.

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 usage in tech/glitch contexts but provides no explicit guidance on when to use this tool over alternatives. No when-not or alternative tool names are given.

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