transform

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

With no annotations, the description carries the full burden of behavioral disclosure. It states it 'sets' values, implying an overwrite, but does not specify what happens to unspecified parameters (likely unchanged, but not stated), whether the operation is reversible, requires a valid handle, or what error conditions exist. Crucial behavioral details are 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, concise and front-loaded with the verb and resource. It uses clear, unambiguous terminology with no superfluous content. Minor structural improvement could be made by explicitly noting that each parameter is optional, but overall it is appropriately concise.

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 no annotations, no output schema, and 0% schema coverage, the description is far from complete. It lacks guidance on parameter formats (array length), handle semantics, behavior when parameters are omitted, and error conditions. Given the tool's mutating nature, an agent needs more context to invoke it correctly.

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 adds meaning to pos, rot, and scale by explaining they are position, Euler rotation (degrees XYZ), and scale. However, it does not specify that arrays must have length 3, nor does it explain the handle parameter. Schema description coverage is 0%, so the description partially compensates but leaves significant gaps in array dimensions and handle semantics.

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 'set' and the resource 'object', and enumerates specific attributes: world position, Euler rotation (degrees, XYZ), and scale. It is explicitly transform-specific and distinguishes itself from generic siblings like set_property by naming exact transformations. The 'and/or' phrasing clarifies partial updates.

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 on when to use this tool versus alternatives. Siblings include set_property, which could be used to modify similar attributes, but the description does not mention any exclusions or preferences. The agent is left to infer usage context without explicit direction.

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