List previously created remesh tasks with pagination and optional ascending or descending creation-date sorting to review past jobs.
List previously created remesh 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, yet it says nothing about pagination defaults, maximum page size, result ordering when sort_by is omitted, or permission/auth requirements. The only behavioral detail is the sort_by value set, which is already in the schema enum.
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. It is under-specified rather than padded, so brevity is not the problem.
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?
A three-parameter list tool with no annotations and no output schema needs the description to cover pagination semantics and return shape, neither of which is addressed. An agent cannot confidently choose paging values or interpret the result.
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% and the description only restates the sort_by enum values without explaining that '+'/'-' mean ascending/descending. page_num and page_size are entirely undocumented in both schema and description.
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 clear verb+resource ("List previously created remesh tasks"). The list_* vs retrieve_*/create_* naming pattern among siblings makes the scope obvious, though the description never explicitly distinguishes itself from retrieve_remesh_task.
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?
It says what the tool does but never when to use it instead of retrieve_remesh_task or how paging should be driven. No exclusions, no prerequisites, no hint about how listing relates to the stream/retrieve siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.