Retrieve previously created animation tasks, sort them by creation date, and use pagination controls to locate specific results.
List animation tasks you have previously created. sort_by accepts '+created_at' or '-created_at'.
| Name | Required | Description | Default |
|---|---|---|---|
| sort_by | No | ||
| page_num | No | ||
| page_size | No |
Changes observed during successful MCP inspections.
v1.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden and does not meet it: it says nothing about default ordering, result limits, whether all historical tasks are returned or only recent ones, or auth requirements. The one useful disclosure is the per-user scoping ('you have previously created'), but the rest of the behavior is opaque.
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?
Two short sentences with no filler, and the core purpose is front-loaded. The second sentence is somewhat redundant with the enum but is harmless.
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 paginated list tool with no output schema, no annotations, and zero parameter documentation, the description should explain what a result looks like and how paging behaves; it does neither. An agent knows roughly what the tool is for but not how to call it well or what it will get back.
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% across three parameters, and the description only restates the sort_by enum values that the schema already defines, adding no meaning. page_num and page_size — the parameters most in need of explanation, such as defaults and maximums — are entirely undocumented.
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?
States a specific verb (list) and resource (animation tasks) and scopes it to tasks the caller previously created. It is distinguishable from retrieve_animation_task by the verb, though the description never names siblings explicitly.
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?
Offers no guidance on when to use this list versus retrieve_animation_task or the stream variants, and no advice on pagination strategy or how many results to expect. The only hint at usage is the phrase 'previously created', which quietly implies a per-user scope.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.