List previously created image-to-3D tasks with sorting by creation date and pagination options to review and manage past generations.
List previously created image-to-3d 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 disclosure burden and largely drops it. It says nothing about pagination behavior, default sort order, result caps, or what fields each task record contains. Only the sort_by value syntax is surfaced.
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 action is front-loaded. The second sentence is slightly redundant with the schema enum but is cheap and reinforces usage.
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 and no annotations, the description should explain paging conventions and result shape. Neither is covered, leaving the agent to guess how to retrieve subsequent pages.
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 3 parameters. The description restates the sort_by enum values already present in the schema (adding no new meaning) and leaves page_num and page_size entirely undefined — no defaults, no maximums, no base index.
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 ('image-to-3d tasks'), which cleanly separates it from the retrieve_*, create_*, and stream_* siblings. It stops short of explicitly naming the retrieve_image_to_3d_task or list_* alternatives, but the resource scoping is unambiguous.
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 indication of when to use this list versus retrieve_image_to_3d_task for a single task, nor any mention of ordering defaults or how to page through results. The agent must infer usage purely from the verb 'List'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.