get_skeletal_mesh_info

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

The description only says 'Get metadata' which implies a read-only operation, but with no annotations the description carries the full burden. It doesn't disclose behavior like valid asset path requirements, error cases, or whether it only works on loaded assets. It adds no behavioral context beyond the name.

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 extremely short and front-loaded with the purpose sentence, followed by a brief parameter line. Every word earns its place, though the Args section is redundant with the schema. It is appropriately concise for such a simple tool.

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 there is an output schema, the description doesn't need to explain return values. However, with no annotations, it lacks any usage context, prerequisites, or behavioral notes. For a one-parameter getter this is minimally viable but not fully complete.

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 no descriptions, so the description adds 'Unreal asset path' which provides minimal extra meaning over the simple 'Asset Path' title. It doesn't explain format or examples, but for a single clearly-named parameter this is below-average yet not absent.

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 states 'Get metadata for a SkeletalMesh' with a clear verb and resource, distinguishing it from the many animation-related sibling tools. It's slightly generic ('metadata') but unambiguous in scope.

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?

No guidance on when to use this tool versus alternatives, no exclusions, and no context provided. It simply states the operation without any situational advice.

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