queryDutyList

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

With no annotations, the description fully shoulders the burden. It reveals internal behavior: reads AndonSysUser config, queries /user/queryPageMap, always includes accountType=0, and describes the mapping of returned fields for saveProjTask. This transparently informs the agent of side-effects and prerequisites.

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, starting with the core purpose in the first sentence, followed by necessary behavioral details. No redundant sentences; every sentence adds value.

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?

Given no output schema and no annotations, the description is fairly complete: it explains input, internal processing, and output usage. However, it does not explicitly mention pagination details (though schema has page/limit). Slight gap but sufficient for the primary use case.

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?

The input schema already has 100% parameter descriptions, so baseline is 3. The description adds value by explaining the filters parameter semantics (keys must be AndonSysUser fields) and the fixed accountType=0 behavior, which is not in the schema. This enhances schema information.

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 explicitly states it queries the project task responsible person list, with a clear purpose: to select the responsible person before calling saveProjTask. This distinguishes it from sibling tools like queryProjUser or queryProjProjectList, which serve different querying needs.

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 clearly indicates when to use this tool (before saveProjTask) and explains how to use the returned data (dutyUserId and dutyUserName). However, it does not explicitly mention when not to use it or compare with alternatives like queryProjUser, which could also query users.

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