gen_uthana_get_motion

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Get... metadata,' which implies read-only behavior, but it does not explicitly state that the operation is side-effect-free or what happens on unknown IDs. The timeout_s parameter is not explained, leaving uncertainty about potential wait behavior.

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 main sentence is efficient and front-loaded, and the example is compact. There is no redundant prose, though the KB link and example consume space that could have been used for parameter details.

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 getter with an output schema, the core purpose and required ID are covered, and the output schema presumably explains return values. However, timeout_s is left unexplained, and there is no sibling differentiation, so the agent may not fully understand when to invoke this tool and what the timeout parameter does.

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 description coverage is 0%, so the description must compensate, but it only provides an example for motion_id and says nothing about the motion_id format or source. timeout_s is completely unexplained; its type and default exist only in the schema, so the description adds minimal value for parameter understanding.

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 a specific verb and resource: 'Get Uthana motion metadata by ID.' This clearly identifies the operation and distinguishes it from other gen_uthana tools like download_motion or get_character, because it targets metadata retrieval specifically.

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?

There is no guidance on when to use this tool versus related tools such as gen_uthana_get_job or gen_uthana_download_motion. The only contextual signal is the phrase 'by ID,' which implies a retrieval use case, but no explicit conditions, prerequisites, or exclusions are given.

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