get_ik_retargeter_info

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered. The description adds useful version-specific behavior: per-op chain mappings and the absence of global RootSettings in 5.8, where detailed root/global settings live inside the ops themselves. It does not cover auth needs or rate limits.

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 followed by the returns structure; the version note is relevant and prevents incorrect assumptions. The returns block is necessary because there is no output schema, and 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?

Complete for a read-only inspection tool: annotations cover the safety profile, the schema covers the only argument, and the description documents the full return shape despite no output schema. The version nuance ensures an agent knows per-op chain mappings are expected.

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% and the single ik_retargeter_path parameter is already documented as the content path to the UIKRetargeter asset. The description adds no parameter-specific syntax or format details beyond what the schema provides, so the baseline of 3 is appropriate.

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 'IK Retargeter' and enumerates scope: source/target IK Rigs, the op-stack, per-op chain mappings, and current poses. The 'global structure' framing distinguishes it from per-op siblings like get_retargeter_op_info and per-chain siblings like get_ik_retarget_chain_details.

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 clear context: read-only, controller-based, and a version-specific routing note that chain mappings are per-op in 5.6+ with no global RootSettings on UIKRetargeter in 5.8. It does not explicitly name alternative sibling tools or when-not-to-use cases, so it falls short of a 5.

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