Retrieve previously created retexture tasks with pagination and sorting by creation time, so you can review or manage past jobs.
List previously created retexture tasks. 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. It reveals that tasks pre-exist and can be sorted, but says nothing about pagination behavior, default sort order, result limits, or what happens when no tasks exist.
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 brief sentences, no filler, with the core purpose front-loaded. Slightly thin rather than padded, but nothing is wasted.
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 schema descriptions, the description should cover pagination defaults and rough return shape. It supplies almost none of that, leaving the agent guessing about the two pagination parameters.
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?
With 0% schema description coverage and no annotations, the description must explain all three parameters. It only mentions sort_by, and even then merely repeats the enum values without explaining that '+' vs '-' means ascending/descending; page_num and page_size 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 and resource: 'List previously created retexture tasks'. It is clearly a collection-listing operation, distinguishable from retrieve_retexture_task and create_retexture_task by the verb, though it never names those 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?
There is no when-to-use, when-not-to-use, or alternative-tool guidance. The phrase 'previously created' vaguely implies it is for browsing existing tasks, but the agent must infer that on its own.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.