batch_transform

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals only that the operation is 'incremental' by default, but does not clarify what incremental means relative to the 'relative' parameter, whether the operation is destructive or reversible, or what happens to existing transform values. For a mutation tool with zero annotation coverage, this is a critical gap.

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 phrase, but this is under-specification rather than conciseness. While it is front-loaded and free of filler, it earns no credit because there is essentially no substantive content to be concise about.

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?

For a 5-parameter tool with 0% schema coverage, no annotations, and no output schema, the description is completely inadequate. An agent cannot determine required inputs, expected behavior, or return values from this definition alone.

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 for the five undocumented parameters (scale, objects, location, relative, rotation). It adds no meaning to any of them - an agent has no idea what values these accept or how they interact (e.g., that 'relative' likely toggles between incremental and absolute transforms).

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 '批量变换（默认增量）' is essentially a translation of the tool name 'batch_transform' plus a vague parenthetical about incremental behavior. It does not state what is transformed (position, scale, rotation), what objects are affected, or how this differs from siblings like set_transform, apply_transforms, randomize_transform, or batch_set_property. This borders on tautology.

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?

There is no guidance on when to use this tool versus the many transformation siblings (set_transform, apply_transforms, randomize_transform, distribute_objects). The '默认增量' (default incremental) note hints at behavior but provides no decision criteria, no prerequisites, and no exclusion conditions.

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