svg_filter_animation

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects on the target element, whether it modifies the DOM or CSS, performance implications, or required permissions. The description is a bare statement of functionality, offering no transparency.

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 very short (one phrase), which is concise but lacks significant content. It does not earn its place by providing necessary details. It could be improved with more structure and information without being overly long.

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 complexity (5 parameters, no output schema, no annotations), the description is severely incomplete. It does not explain what 'filter animation' entails, how parameters interact, what the result looks like, or any return value. An agent would struggle to invoke this tool correctly based solely on the description.

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 input schema covers 80% of parameters with descriptions (target, toValue, fromValue, filterType have descriptions; duration has a default but no description). The tool description adds no additional meaning beyond the schema. With high schema coverage, the baseline of 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 states 'SVG滤镜动画效果' which indicates it applies SVG filter animation effects. This is somewhat specific but very brief; it does not differentiate from siblings like svg_morph_animation or generate_gsap_animation. The verb 'animate' is implied, and the resource is SVG filters, but the description lacks clarity on what exactly changes.

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 description provides no guidance on when to use this tool versus alternatives such as generate_gsap_animation, which covers general animation, or other SVG-specific tools. There is no mention of prerequisites, limitations, or exclusions, leaving the agent without context for selection.

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