updateProjTask

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

No annotations provided, so description carries full burden. It discloses the underlying API call and parameter dependencies, but lacks details on error behavior, response format, or whether the operation is reversible. Moderate transparency for a mutation tool.

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?

Three sentences, each essential and well-structured. Front-loaded with purpose and prerequisite. No redundant information, highly efficient.

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 13 parameters and no output schema, the description adequately covers update operation and special parameter rules. However, it lacks information on return value, error handling, and whether updates are partial or full. Could be more complete for a complex tool.

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 covers all 13 parameters with descriptions. The tool description adds significant value beyond schema by explaining usage rules: only pass modified fields, id must come from queryProjectTask, duty fields must come together from queryDutyList. This enhances parameter understanding.

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 the tool modifies project task information and refers to the specific API endpoint. It distinguishes itself from siblings like saveProjTask (create) and deleteProjTask by focusing on update, and mentions prerequisites that differentiate usage from query tools.

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?

Explicitly states prerequisite of calling queryProjectTask first, and instructs to only pass modified fields. Provides specific constraints for dutyUserId/dutyUserName. Does not explicitly mention when not to use (e.g., for creation), but this is implicit given sibling context.

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