transform_component

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

No annotations provided, so the description carries full burden. It does not disclose whether the transform overwrites or accumulates, whether it is destructive, or any side effects like triggering recomputation. Critical behavioral context is missing.

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, which is concise but lacks structure. It could be improved by breaking into bullet points or adding context, but it is not overly 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 no annotations and an output schema that exists, the description should cover basic operational semantics and input details. It fails to explain that the component must exist, what the output entails, or how the parameters interact (e.g., can all be set at once). Incomplete for the tool's complexity.

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 description merely lists the parameter names (position, rotation, scale) without adding any semantic meaning. It does not explain the array format, that null means no change, or the units. With 0% schema description coverage, the tool description should compensate but fails.

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 specifies the verb 'Transform' and the resource 'component', and lists the affected properties (position, rotation, or scale). This clearly distinguishes it from siblings like create_component or delete_component, but it lacks precision on whether the transform is absolute or relative.

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 on when to use this tool versus alternatives. For example, it does not mention that this is the tool for moving/rotating/scaling an existing component, nor does it state any prerequisites like component existence.

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