transform_component

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 implies mutation but does not state whether the transform fully replaces existing values, whether the component must already exist, or whether the operation is reversible. No errors, permissions, or side effects are mentioned.

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, front-loaded sentence with no filler or irrelevant content. It conveys the core purpose in eight words, and every word contributes to the meaning. This is an appropriately concise and efficiently structured definition.

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 tool with four parameters (one required, three optional arrays) and no annotations, the description is underspecified. It lacks details about array formats, whether multiple transforms can be combined in one call, and the meaning of default null values. Though an output schema exists, key operational details remain missing.

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%, and the description offers minimal compensation. It repeats the parameter names 'position', 'rotation', and 'scale' without explaining array structure, units, coordinate order, or whether rotation is Euler angles or a quaternion. This gives an agent slightly more context than the schema alone, but not enough to construct valid parameter values.

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 uses a specific verb ('Transform') and resource ('a component'), and explicitly lists the affected properties: position, rotation, or scale. This clearly identifies the tool's function and separates it from siblings like create_component or set_material. However, it does not explicitly differentiate from alternatives or state whether it modifies an existing component versus creating a new one.

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 alternatives such as create_component, delete_component, or set_material. The description only states what the tool does, leaving usage conditions entirely implicit. No exclusions, prerequisites, or alternative tool references are provided.

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