queryProductionTaskList

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

Given no annotations, the description discloses the internal flow (two API calls, data dictionary translation) and notes that the returned context includes record IDs. It does not explicitly state read-only behavior, but as a query tool it is implicitly safe. The description adds value beyond the annotations gap.

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 concise (3 sentences), front-loaded with the main purpose, and every sentence adds necessary detail. No fluff or redundancy.

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?

The description explains the internal flow and mentions that returned records include IDs, but lacks details on pagination metadata (e.g., total pages) or complete response structure. Since no output schema exists, more detail on the return format would be beneficial.

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%, baseline 3. The description adds value by explaining the filters parameter format (fuzzy text, range for time fields) and the purpose of contain/exclude for field initialization, which goes beyond the schema descriptions.

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 clearly states '分页查询生产任务列表' (paged query for production task list), specific verb+resource. It distinguishes from sibling tools like auditProductionTask (audit) and dispatchToStation (dispatch) by being a query-only tool, which is evident from the context.

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 usage for listing production tasks with pagination, but does not explicitly state when to use this tool compared to siblings like querySopList or queryWorkstationList. No exclusions or alternatives provided.

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