transform_3d_animation

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

No annotations are provided, so the description must disclose behavior. It fails to mention what the tool does (e.g., applies CSS 3D transforms, animates, etc.), whether it is destructive, or what the output is. The agent has no insight into the tool's effects.

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 (one word in context), which is not conciseness but under-elaboration. It fails to earn its space as it provides no useful information beyond the tool name.

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?

With 7 parameters, no output schema, and no annotations, the description is woefully incomplete. An agent cannot determine how to invoke this tool correctly or what to expect from it.

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 only 14% (only 'selector' has a minimal description). The tool description adds no additional meaning to the parameters; the agent must infer their purpose from names like 'rotationX' and 'translateZ', which is insufficient for correct usage.

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 '3D变换动画' is a tautology of the tool name, providing no additional specificity. It does not distinguish this tool from siblings like 'camera_3d_animation' or 'scene_3d_animation', which also involve 3D animations.

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 guidance is given on when to use this tool vs alternatives. The description lacks any context about prerequisites, typical use cases, or conditions that would indicate this tool is appropriate.

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