set_static_mesh_socket_transform

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

Annotations already declare the safety profile (not read-only, idempotent, destructive). The description adds genuinely new behavioral context: partial-update semantics ('only the provided fields'), an input-validation rule ('not three numbers is an error'), and the return contract including 'updated'/'saved' flags. No contradiction with the annotations.

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 the action and scope, followed by the validation rule and a compact return shape. Every element earns its place, though the 'Returns:' block stacks flag fields ('updated', 'saved') whose meaning is left unexplained.

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?

With no output schema, the description usefully supplies the return shape, and annotations already cover the safety profile for a mutation tool. It documents partial-update behavior and validation, leaving only edge cases (e.g., what 'saved' implies, failure modes) unaddressed.

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 description adds a validation constraint ('a location, rotation or scale that is not three numbers is an error'), but that rule sits awkwardly against the schema, which explicitly permits an object form for rotation. Reference rather than genuine enrichment.

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?

States a specific verb and resource: 'Update the relative transform of an existing static mesh socket.' This is distinguishable in effect from siblings like add_static_mesh_socket, remove_static_mesh_socket and set_skeletal_mesh_socket_transform. It never explicitly names those siblings, so it falls just short of full sibling differentiation.

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?

The phrase 'existing static mesh socket' implies the socket must already exist, but the description gives no explicit when-to-use guidance, no prerequisites, and no routing against alternatives such as add_static_mesh_socket or set_skeletal_mesh_socket_transform. Usage is only faintly implied.

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