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

Annotations only declare idempotentHint and destructiveHint=false; the description adds substantial context the agent cannot infer: an authentication requirement, a role-based permission restriction, serial execution with frequent partial success, and the fact that the result reports updated/failed counts that must be relayed honestly to the user. The rule '不能替别人宣称完成——只按用户明说的改' is an important safety constraint that no structured field conveys.

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 permission and data-source facts are front-loaded and every clause carries operational weight, with no filler. The telegraphed, semicolon-chained phrasing and the trailing note about AI assignment suggestions make it slightly denser than it needs to be, but it stays compact for the amount of information delivered.

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 batched mutation with no output schema, the description covers everything an agent needs: auth, role scoping, ID provenance, batch nature, partial-failure expectations, and how to report the updated/failed result. No significant operational question is left open.

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 the baseline would be 3, but the description earns above baseline by explaining where the organizationId and taskId values come from (list_my_organization_tasks items) and by framing items as a batch. It does not repeat the per-field limits (max 50, maxLength) already in the schema, which is correct restraint.

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 names a specific verb and resource ('改组织任务状态') plus the exact state enum TODO/DOING/DONE/CANCELLED and the batch capability, so the operation is unmistakable. It further separates itself from create_organization_task by stating that tool is for managers assigning new tasks. It does not distinguish itself from the close sibling set_collaboration_task_status, which keeps it from a 5.

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 names the prerequisite (登录), the permission boundary (非管理者只能改派给自己的那些), the upstream data source (list_my_organization_tasks → items[].{organizationId,id}), and an explicit alternative for the adjacent need (create_organization_task for new assignments). It even excludes a related use case ('AI 分工建议仍只在 App／网页'), which is a genuine when-not-to-use statement.

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