get_anim_sequence_info

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

With no annotations provided, the description carries the burden. It discloses the full set of return values and the asset_path format, which implies a read operation. However, it does not explicitly state that it is read-only, nor does it mention error behavior or prerequisites, leaving some ambiguity.

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 tight and well-structured: a one-sentence purpose, a bulleted list of returns, and a parameter explanation. Every part earns its place, with no filler or redundancy.

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 simple one-parameter getter with an output schema present, the description covers purpose, parameter format, and return fields. It lacks explicit error-handling details or contrast with sibling tools, but those are not essential here, so it is nearly 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 input schema only says 'string' for asset_path, so the description adds significant value by explaining it as an 'Unreal asset path' and providing a concrete example ('/Game/Animations/AS_Run'). This goes beyond the schema and helps the agent format the parameter 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 uses a specific verb 'Get' with the resource 'AnimSequence' and enumerates exactly what metadata is returned (length, frame count, rate scale, etc.). This clearly distinguishes it from sibling getters that target narrower aspects like sync markers, curves, or bone tracks.

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 implies use when one needs core metadata for an AnimSequence, listing the fields returned. However, it lacks explicit guidance on when to prefer this over more specific getters (e.g., get_bone_tracks, get_anim_curves) and provides no exclusions or alternatives.

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