get_skeleton_info

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

With no annotations provided, the description carries the burden of conveying behavioral traits. 'Get' implies a non-mutating read operation, but the description does not explicitly state that it does not modify the asset, whether asset existence is checked, or any error conditions. It provides minimal but acceptable transparency for a simple getter.

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?

The description is two sentences: a clear statement of purpose and a parameter explanation. Every sentence earns its place, and it is front-loaded with the core functionality. No redundancy or 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?

Given the tool's simple nature (one parameter, read-only action), and the presence of an output schema, the description is largely complete. It could benefit from mentioning that it works with Unreal asset paths, but that is already implied by the parameter description. It covers what the tool does adequately for a basic getter.

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?

The schema only defines 'asset_path' as a string with no additional description. The description adds 'Unreal asset path', clarifying the expected format. However, this is still minimal and does not elaborate on path syntax or provide examples, so it only partially compensates for the 0% schema coverage.

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?

The description clearly states the tool retrieves bone hierarchy and metadata for a Skeleton. The verb 'Get' plus the specific resource 'Skeleton' distinguishes it from the sibling tools that operate on other asset types like meshes, animations, and montages.

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 description provides no guidance on when to use this tool versus alternatives. It does not compare against sibling tools such as get_skeletal_mesh_info or get_anim_sequence_info, nor does it state any exclusions or prerequisites. The only implied usage is from the tool's name and purpose.

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