list_multi_image_to_3d_tasks

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

No annotations are provided, so the description carries the full behavioral burden. 'Previously created' hints at read-only persistence, but it never states that listing is non-destructive, how pagination behaves, what defaults apply, or what a result entry contains.

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, front-loaded with the tool's purpose, with the sort detail following. Every sentence carries information, though the sort sentence largely duplicates the enum in the schema.

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?

With no annotations, no output schema, and 0% parameter documentation, the description leaves too much unspecified for a paginated listing tool — result shape, default page size, and total-count semantics are all absent.

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 for all three parameters. It only addresses sort_by, and even that mostly restates the enum ('+created_at'/'-created_at'); page_num and page_size receive no mention, so default page size and paging limits remain unknown.

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 ... multi-image-to-3d tasks') with the scope qualifier 'previously created'. The list/retrieve/create/stream/delete family is distinguishable by the verb alone, so an agent can route correctly, though the description never names a sibling 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?

The verb 'List' implies a collection-browsing use case, and the tool filling a role between retrieve_multi_image_to_3d_task and delete_multi_image_to_3d_task is inferable. There is no explicit when/when-not guidance or stated prerequisite (e.g., that the user must already have created tasks).

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