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

The readOnlyHint annotation already establishes that this is a safe read, so the lower bar applies. The description adds real business context beyond annotations — that claiming a task and submitting results cost nothing and payment happens only when the publisher confirms and pays voluntarily — but says nothing about result volume, pagination, ordering, or what a returned task contains.

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?

Two compact sentences: the first front-loads what the resource is and then enumerates the two filter behaviors, the second covers the payment model. No filler, though the semicolon-chained clause makes it slightly dense to parse.

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 read-only four-parameter lister with no output schema, the definition supplies the domain framing, both non-obvious boolean filters, and the zero-cost/voluntary-payment model that an agent needs to describe results correctly. Missing detail on q and pagination is minor against the annotation already covering the safety profile.

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%, so the description must carry parameter meaning, and it does explain two of four parameters well: includeNetwork (org-only scoping) and mine (published-or-accepted by me). The required organizationId is only implied by '组织内' and the free-text q parameter is never mentioned, so the compensation is partial rather than complete.

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 resource concretely, listing the three content categories (互帮互助、项目、人脉引荐任务) and the scope ('组织内优先'), so the agent knows what will be listed. It never says 'list/query' explicitly (that comes from the name/title) and never distinguishes this from sibling listers such as list_my_organization_tasks or get_ecosystem_task, leaving the family routing implicit.

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 two conditional filter behaviors (includeNetwork=false → only this org; mine=true → things I published or accepted), which effectively tells the agent when to flip those switches. It gives no guidance about when to call this tool versus list_ecosystem_activities, list_my_organization_tasks, or get_ecosystem_task for a single record, so sibling selection is left to inference.

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