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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description adds real context beyond them: reading tasks idempotently backfills cycle periods, so the call is 'not purely read-only', plus caps (invitations max 50) and the login requirement. It stops short of describing exactly what records get created by the backfill or in what order results are merged, so it is strong but not exhaustive.

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?

Nearly every clause carries actionable information and the contents enumeration is front-loaded before the routing rules. The telegraphic semicolon chains and the stray leading '登录;' fragment make it harder to parse than it needs to be, but there is little genuine filler.

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 no-output-schema, no-required-param aggregate over three resource types, the definition covers contents, pagination, caps, side effects, and sibling routing. The only material omission is includeArchived, which is undocumented in both schema and description.

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 description coverage is 0% across three parameters, so the description must carry the burden. It documents goalOffset pagination semantics and the invitation cap that relates to limit, but says nothing about includeArchived or the interaction between limit and the goals/tasks collections.

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 the exact three resources returned: collaboration goals, the caller's assigned dispatch tasks, and pending cooperation invitations. It immediately contrasts scope with get_my_dispatch ('does not read/mark arrangements'), so an agent can separate the two aggregate tools without opening schemas.

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?

Explicit routing is given for each alternative: arrangements go to get_my_dispatch, single goals to get_collaboration_goal, status reporting to set_collaboration_task_status, invite responses to respond_collaboration_invite. It also states the negative case ('goalId=null tasks are directly assigned, do not call goal tools') and the escalation path when tasks hit reachingLimit (query list_collaboration_tasks by goalId).

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