cst_transform_translate

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

No annotations provided, so the description carries the burden. It indicates the tool can move or copy a solid, but does not clarify if the original is modified by default, what happens to the original when copying, or any return value. The ambiguity around destructive behavior lowers the score.

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 short sentence that conveys all key information without redundancy. It is front-loaded and efficient.

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?

The description covers the tool's purpose and parameters but lacks information about return values, side effects, or prerequisites. With no output schema, the agent is left uncertain about what the tool provides after execution.

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 coverage is 100% with each parameter described. The description adds minimal value beyond the schema, grouping dx, dy, dz as a displacement vector and noting the copy option. It does not introduce new meaning not already in 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 the verb 'Translate (move)' and the resource 'a solid', specifying the displacement vector as (dx, dy, dz). It distinguishes from sibling tools like cst_transform_rotate or cst_transform_scale by focusing on translation.

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 implies when to use this tool (for moving solids) and briefly mentions the optional copy feature, but does not explicitly state when not to use it or compare to alternatives. Given sibling names, the context is clear enough.

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