分页查询任务列表

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

With no annotations, the description carries the transparency burden. It discloses that this is a read-only query operation ('查询') and that it is paginated ('分页'), which is useful. It does not add deeper behavioral context like permission requirements, result ordering, or total-count behavior, and it largely repeats the filter options already present in the schema.

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?

The description is a single compact sentence that front-loads the core purpose and then enumerates the filter options. It is minimal and contains no redundant information.

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 list tool with no output schema, the description adequately conveys the core purpose and filter capabilities. It does not describe the response structure, but 'list tasks' makes the output obvious. Given the tool's simplicity and the schema covering parameter details, it is sufficiently complete.

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 100% (all 7 parameters have descriptions), so the baseline is 3. The description lists the same filter categories (executor group, status, task description, JobHandler, author) but does not provide additional semantic value beyond what the schema already defines.

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?

The description begins with '分页查询 XXL-JOB 任务列表' (paged query of XXL-JOB task list), which clearly states the verb (query), resource (task list), and pagination aspect. It also lists specific filter criteria, distinguishing it from sibling tools like get_job (single job) and list_job_groups (executor groups).

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 description implies its use case by stating it supports filtering by various criteria, making it clear this is the general list/query tool. However, it does not explicitly mention alternatives or provide when-not-to-use guidance, such as pointing to get_job for single-job retrieval.

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