saveProjTask

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

With no annotations, the description carries full burden. It discloses that progress and delayDays are fixed to 0, and mentions the underlying API call. However, it does not discuss side effects, authorization requirements, or error conditions, but the detailed prerequisites provide sufficient behavioral context for correct invocation.

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 paragraph that front-loads the action and then lists prerequisites sequentially. It is concise for the amount of information provided, though slightly run-on. 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 10 parameters, 5 required, and no output schema, the description covers prerequisite steps and fixed fields. However, it does not explain the return value or error handling, leaving some gaps for the agent regarding what happens after invocation.

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 coverage is 100%, so each parameter has a description. The tool description adds overall context about the origin of certain parameters (e.g., from prior queries) but does not add meaning beyond what is already in the schema. Baseline 3 is appropriate.

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 the tool is for adding new project tasks or subtasks, using the verb '新增' (add) and resource '项目任务或子任务' (project task or subtask). It distinguishes itself from sibling tools like updateProjTask and deleteProjTask by focusing on creation.

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 provides explicit prerequisites: must call queryProjProjectList first for projectId, queryDutyList for dutyUserId and dutyUserName, and queryProjectTask for parentId when adding subtasks. It also states that progress and delayDays are fixed to 0, giving clear when-to-use guidance.

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