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

Annotations only declare idempotentHint and destructiveHint=false, and the description adds substantial context on top: login/member permission requirement, a 200-item cap with a possible reachingLimit truncation, includeClosed semantics, and the partial-failure behavior where non-initiators get null plus owner_only instead of a whole-request error. Those are exactly the traits an agent cannot infer from annotations. The phrase '读任务幂等补周期' is too compressed to be useful, which keeps it from a 5.

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?

It is compact and front-loads the permission constraint, and the arrow notation for follow-up tools is effective. However, it is a single semicolon-chained run-on with compressed fragments ('读任务幂等补周期', '不整条报错') that cost parse time. Dense is not the same as well-structured.

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?

There is no output schema, so the description has to describe returns, and it largely does: goal body plus tasks by default, extra blocks via include, truncation signaling via reachingLimit, and the owner_only/null shape for invites. Remaining gaps are minor (no pagination cursor details), but the essential shape is present.

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 only 33% (only 'include' is documented), so the description must compensate, and it does: it defines includeClosed as including closed items, and explains each include enum value — recruits with its displaying/isMember/invitePending computed fields, activities as attached activities, series, and invites with its initiator-only visibility rule. That is meaning well beyond the raw schema.

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 opening clause '读目标/本人权限/合作人/任务' names the concrete resources returned (goal, caller permissions, collaborators, tasks), which is more specific than the title alone. It also distinguishes itself from create_collaboration_task and update_collaboration_goal by pointing at them for writes. It loses a point only because the telegraphic phrasing means the agent must decode it rather than read a plain statement of purpose.

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 gives per-block guidance: use 'include' on demand for recruits/activities/series/invites, and each block routes to the follow-up tool (invite_collaboration_member, update_task_series/stop_task_series, cancel_collaboration_invite). It also states the access condition 'invites仅发起人'. It does not mention the sibling list_collaboration_tasks as an alternative way to read tasks, so the when-not-to-use side is incomplete.

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