set_absolute_transform

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=true, so the mutation/idempotency profile is covered structurally. The description still adds real value with the non-obvious 'does NOT call Modify(), so pair it with another dirtying edit or the save may skip the actor' caveat and the required-flag error behavior. However, it doesn't explain the destructiveHint=true marking (whether prior absolute-flag state is lost, whether it's reversible), which the annotation raises but the description leaves unaddressed.

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?

Front-loaded with purpose, then constraints, read-back guidance, and the Modify() caveat; every sentence carries weight. The prose is dense with parentheticals and could be slightly tightened, but there is no filler.

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?

Though there is no output schema, the description fully specifies the return shape (applied, actor_name, and all three flags re-read off the root component). Combined with the doctored requirements and the save/Modify caveat, an agent has everything needed to call and interpret 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?

Schema coverage is 100%, so the baseline is 3; the schema documents each of the three flags and their inherited-vs-absolute meaning. The description adds a constraint the schema lacks: at least one of the three flags must be supplied or it errors, since the schema only marks actor_name as required.

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?

Names the specific verb+resource ('make an EDITOR-world actor's root SceneComponent use ABSOLUTE (world-space) location/rotation/scale') and immediately contrasts it with inheriting from a parent. It clearly differentiates from the sibling read tool by pointing to get_absolute_transform for reads.

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?

Gives the exact condition that selects it ('an attached actor that drifts or shears when its parent moves or is scaled'), names the read-back alternative (get_absolute_transform), and prescribes a pairing rule (combine with another dirtying edit). When-to-use, alternative, and caveats are all explicit.

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