get_usd_world_transform

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

With no annotations, the description carries full burden and does disclose real behavior: each frame recooks the stage, rotate is XYZ degrees, output is translate/rotate/scale plus a row-major matrix, and the playbar is restored (a side effect that matters). This is meaningful beyond-name disclosure, though it omits permissions/cost context.

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-loads the purpose, then differentiation, then output shape, then args. Every sentence contributes; slightly verbose but 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?

With no output schema and no annotations, the description fills both gaps by describing the returned components and the playbar-restore side effect. Complete enough to call correctly, missing only cost/latency or failure-mode context.

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%, so the description must compensate, and it does: node_path is 'LOP node whose stage to read', prim_paths gets an example ("/world/cam"), and frames is capped 'at most 500' with a default of the current frame. All three params get constraint-bearing text.

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+resource (world transform of USD prims) and scope (one or more frames), and explicitly distinguishes itself from get_usd_prim by noting that it composes every parent so animated parents show. An agent can tell it apart from the sibling without opening a schema.

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?

Names the alternative, get_usd_prim, and the condition that selects it: local xformOps versus composed world transform. That is clear routing guidance, though it stops short of an explicit 'when-not-to-use' statement or prerequisites.

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