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

Goes well beyond the annotations by disclosing login + member-permission requirements, a 200-item cap with a 'reachingLimit' truncation flag, idempotent behavior, and — importantly — that reading tasks lazily '补周期', which explains why readOnlyHint is false for a 'get' tool rather than contradicting it. It also documents the permission-based null + owner_only return for non-initiators.

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?

Front-loads the critical auth/permission constraint and contains no filler — every fragment carries information. The tradeoff is a dense run-on punctuated with slashes and arrows that is harder to parse than a cleanly structured definition.

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 moderate-complexity read with no output schema, the description adequately sketches the returned structure (goal body + tasks, plus the optional blocks and their fields), so an agent knows what to expect. It stops short of fully enumerating return fields, but that is a minor gap.

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?

With only 33% schema coverage, the description carries the load: it explains includeClosed ('含了结'), interprets each include enum value (recruits/activities/series/invites) and even the sub-fields (displaying, isMember/invitePending) plus which tool consumes each. This adds substantial meaning beyond the bare 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 '读目标/本人权限/合作人/任务' states a specific verb (read) and the resource set (goal, own permissions, collaborators, tasks), and the rest of the text names sibling tools for the adjacent actions. The core purpose is clear, though it is somewhat buried inside heavy routing content rather than stated as a single crisp sentence.

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 tells the agent when to use each optional block ('include按需取...') and routes to specific alternatives with their trigger conditions: recruits→invite_collaboration_member, series→update_task_series/stop_task_series, invites→cancel_collaboration_invite, task creation→create_collaboration_task, goal edits→update_collaboration_goal. This is a full when/when-not/alternative map.

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