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

Goes well beyond the annotations by disclosing the key side effect: collaborators on the goal immediately gain management rights over the activity, plus an explicit authorization-scope warning and the login requirement. The non-idempotency implied by that grant is context the annotations alone (destructiveHint=false) do not convey. No contradiction with the declared hints.

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?

Very dense and front-loaded with the login gate and the side-effect warning ahead of the workflow steps. Every clause carries information, though the single run-on sentence with multiple semicolon clauses is slightly harder to parse than a clean multi-sentence layout.

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 mutation tool with no output schema, it covers auth, the permission-granting side effect, where to get the activity reference, a post-condition verification step, and the ownership constraint. Only goalId's expected format/meaning is left unexplained.

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 50%: activityRef is documented in the schema and the description usefully adds 'attachable' as an alternate source, but goalId is undocumented in both schema and description. The description adds some value for activityRef without fully compensating for the gap on goalId.

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?

States a specific verb ('挂到' = attach) and resource ('本人活动' → '合作目标'), and its directionality immediately distinguishes it from the sibling detach_activity_from_goal. An agent can tell what this does without opening the schema.

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?

Gives concrete workflow context: the activity reference is sourced from list_my_activities or 'attachable', and results should be verified with get_collaboration_goal afterward. It also states a clear when-not ('不能代挂他人活动'). It stops short of naming the reverse sibling (detach_activity_from_goal) as the alternative, so not a full 5.

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