cocos_set_node_position

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

No annotations are provided, so the description carries full burden. It implies a mutation ('Set'), but does not disclose behavioral traits like whether it requires specific permissions, if changes are reversible, or potential side effects (e.g., affecting child nodes). The z default is useful but insufficient for a mutation tool.

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 a single, efficient sentence that front-loads the core action and includes essential parameter context (z default). There is no wasted verbiage, making it highly concise and well-structured.

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 5 parameters with 0% schema coverage and no annotations, the description is incomplete—it only addresses the z parameter's default. An output schema exists, so return values need not be explained, but for a mutation tool with undocumented parameters, more context is needed for adequate completeness.

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 0%, so the description must compensate. It adds meaning by explaining that z defaults to 0 for 2D scenes, which clarifies one parameter's behavior. However, it does not explain the semantics of other parameters like 'scene_path' or 'node_id', leaving gaps.

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 the verb 'Set' and resource 'node's local position' with specific coordinates (x, y, z), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'cocos_move_node' or 'cocos_set_node_rotation', which would require a 5.

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 (e.g., 'cocos_move_node' for relative movement or 'cocos_set_node_rotation' for other transformations). It mentions a default for z in 2D scenes, but this is a parameter detail, not usage context.

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