batch_set_location

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

The description adds minimal context beyond the annotations: it says 'all objects' but provides no detail on how the vector applies (absolute vs. relative), whether objects are moved or offset, or any side effects. The destructiveHint is present, but the description doesn't elaborate on what may be lost or changed.

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 incomplete sentence in German, under-specified for a destructive batch operation. It lacks structure and does not front-load useful semantics; it is not concise but rather insufficient.

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?

Despite low complexity (one optional parameter, output schema exists), the description is too sparse. It fails to convey that this is a destructive mutation tool acting on all objects, and it doesn't describe the expected behavior (e.g., does it replace all locations or add an offset?). The output schema could clarify returns, but the description still needs more context.

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 schema has 0% description coverage for the 'offset' parameter. The description only mentions 'met vektor' (with vector), which weakly hints that offset is a vector, but it doesn't explain the required format (e.g., array of three numbers), units, origin, or how it interacts with existing positions.

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 'Geser alle objekte met vektor' suggests moving all objects by a vector, which roughly matches the tool name 'batch_set_location'. However, it is vague about whether it sets absolute positions or applies an offset, and it doesn't distinguish from sibling tools like 'batch_set_scale' or 'transform_object'.

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 about when to use this tool versus alternatives such as 'apply_transforms_all' or 'transform_object'. There is no mention of prerequisites, selection requirements, or exclusions.

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