get_global_transform

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful nuance that the returned coordinates are evaluated world-space values with a default-to-current-frame behavior, but does not discuss frame-scoped evaluation semantics or what happens for invalid frames.

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?

A single front-loaded sentence with no filler, though the telegraphic phrasing ('at frame, default current') reads more like a note than a definition and slightly obscures the default-frame meaning.

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?

Since there is no output schema, the description must imply the return shape, and 'position/quaternion' does that minimally. It leaves gaps around identifier format, frame bounds handling, and how the result relates to keyframed vs evaluated transforms.

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 0%, so the description carries the burden, and it does document that 'frame' is optional and defaults to the current frame — information absent from the schema's min/max bounds. However, it never clarifies the 'object' parameter's expected identifier form even though it is the only required parameter.

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 ('Read') and resource ('actual world position/quaternion'), and the word 'world' implicitly distinguishes it from get_local_transform among the siblings. It stops short of naming the sibling it differs from, so an agent must still infer the local-vs-world split.

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 only usage information is that frame defaults to current. There is no statement of when to prefer this over get_local_transform, get_transform, or get_pose, all of which sit in the same sibling cluster.

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