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

Only destructiveHint=false is supplied by annotations, and the description fills the real gap: creation is non-atomic ('前成功不因后失败回滚'), results come back bucketed as created/failed, every task pushes a notification to its assignee, login is required, and there is a practical cap rationale. These side-effect and partial-failure semantics are exactly what an agent cannot infer from the schema or annotations.

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?

Extremely dense but front-loaded — login and batch scope come first, then the preview workflow, then failure semantics, defaults, and preconditions. Every clause carries information, though the telegraphic semicolon chaining makes it slightly harder to parse than prose would be.

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 3-parameter mutation tool with no output schema, this covers everything an agent needs: auth requirement, batch cap, preview-vs-commit workflow, non-atomic failure behavior, result shape, notification side effects, and assignee defaulting. Nothing material is left to guesswork.

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 67% and the description adds genuine meaning beyond it: preview=true is framed as a permission/member check rather than a dry-run flag, and assigneeId defaults to the caller with a non-member precondition. The ≤10 limit and the preview return shape are already in the schema, so some repetition exists.

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 states a specific verb and resource with a clear scope: batch-assign tasks under the same goal, capped at 10. It implicitly distinguishes itself from the singular create_collaboration_task sibling through '批量', but never names that sibling explicitly, so an agent must infer the single-vs-batch split.

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?

Strong operational guidance: preview=true to verify permissions and target members before confirming, preview=false to actually create, plus a prerequisite rule (invite non-members via invite_collaboration_member first) and a social rule (ask about merging when one person exceeds 3 tasks). What's missing is explicit routing versus the singular or direct-collaboration creation siblings.

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