godot_animation

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

No annotations exist, so the description must convey behavioral traits. It mentions operations like delete and create but does not disclose whether they are destructive, require permissions, or have side effects. The agent lacks critical safety information.

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 concise, fitting key information (actions, example path) in a single sentence. It is front-loaded with purpose. However, the brevity sacrifices necessary detail, which is a trade-off.

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 tool's multiple actions and the mysterious 'params' parameter, the description is grossly incomplete. It offers no output schema, no return value information, and no hints about parameter usage or action-specific behavior. An agent cannot reliably use this tool.

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 has two parameters (action and params) with 0% schema description coverage. The description lists possible action values but does not explain the 'params' parameter, its structure, or how it interacts with each action. This is a major gap for tool invocation.

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 it handles 'AnimationPlayer ops' and lists specific actions like list, get, create, etc., along with an example path. This sufficiently distinguishes it from sibling tools like godot_node_read or godot_scene, though it could be more precise about the resource being manipulated.

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 lists actions but provides no guidance on when to use each action or how this tool compares to alternatives (e.g., godot_node_edit). There is no 'when to use' or 'when not to use' context, leaving the agent to guess based on action names.

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