get_skeleton_bone_names

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

With no annotations, the description carries the burden, and it does well by implying a read-only query with List and by documenting the exact return keys: success, bone_count, bone_names, message. It does not explicitly confirm the operation is side-effect-free or describe failure behavior, but for a simple query this is adequate.

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 purpose is front-loaded, then usage context, Args, Returns, a KB pointer, and an example follow. Every section earns its place 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?

For a one-parameter query tool with an output schema, the definition is complete: it specifies the path format, the return contract, and a runnable example. No critical call-time information is missing.

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 has 0% description coverage, but the Args section fully documents the single parameter as a Content path to the Skeletal Mesh with a concrete example path. The agent has everything needed to populate skeletal_mesh_path correctly.

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 opens with a specific verb and resource: List all bone names in a Skeletal Mesh's skeleton. It further ties the purpose to IK Rig retarget-chain setup, which differentiates it from the broad animation/mesh sibling set.

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?

It gives a clear invocation context: use this before setting up an IK Rig to discover the exact bone names required for retarget chains. It does not state when not to use it or name alternatives, so it stops 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.