rhino_move

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

The description mentions translation and optional copying, but does not explain whether the original objects are replaced when copying (make_copy parameter). Annotations already indicate readOnlyHint=false, so the description adds little beyond that.

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 sentence with 10 words, which is very concise. It is front-loaded with the core action, but could benefit from slightly more detail without becoming verbose.

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 of a move tool with a vector input and an output schema, the description is too brief. It does not explain the vector format, the effect of the make_copy parameter, or what the tool returns (e.g., moved object IDs).

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% because the tool description does not mention parameters. However, the input schema itself provides descriptions for all parameters, so the baseline is 3. The description adds no extra meaning beyond the schema.

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 translates or copies objects by a vector, which is a specific verb and resource. However, it does not differentiate from sibling transform tools like rhino_rotate, but the verb 'translate' is distinct enough.

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 provided on when to use this tool vs alternatives such as rhino_rotate or rhino_mirror. The presence of many sibling tools for various transformations makes this a significant gap.

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