text_path_animation

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

No annotations are provided, and the description lacks any behavioral disclosure. It does not state whether the action is read-only or destructive, what effects occur (e.g., animation playback), error handling, or required permissions. The agent has no insight into side effects or safety.

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 extremely short (4 characters in Chinese), which is under-specification rather than conciseness. It contains no actionable information. Every sentence should earn its place, but this description provides nothing useful.

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 absence of output schema and annotations, the description should compensate with rich behavioral and usage context. With 4 parameters and many sibling tools, the description is completely inadequate. It fails to explain what the tool returns or how it behaves, leaving the agent unable to use it correctly.

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?

Schema description coverage is 75% (3 of 4 parameters have descriptions in the schema), so the baseline is 3. However, the tool description adds zero value beyond the schema—it does not explain parameter relationships, formats, or constraints. The schema descriptions are minimal (e.g., 'SVG路径数据'), and the tool description should have supplemented them, but it does not.

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 is a Chinese translation of the tool name ('文本路径动画' = 'text path animation'), providing no additional clarity. It is essentially a tautology, repeating the name without explaining the tool's function or its distinction from sibling tools like 'svg_path_animation'.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives such as 'svg_path_animation' or 'text_reveal_animation'. There is no mention of prerequisites, use cases, or exclusions.

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