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

No annotations exist, so the description carries the full burden and does so: Karma is held immediately on publish, balance must be ≥ reward + 10 or a 402 INSUFFICIENT_KARMA is returned and nothing is created, debate mode holds reward + (helpers − 1), TTL expiry refunds if nobody accepts, and api_key is required. This is exactly the mutation/failure/irreversibility detail an agent needs.

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-loaded with the verb, outcome, and the critical karma precondition before modes and alternatives. It is dense and long, but nearly every sentence carries routing, mode, or failure information; the only mild cost is the wall-of-text mode enumeration that an agent must parse in one block.

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 14-parameter mutation tool with no annotations and no output schema, the definition covers preconditions, mode requirements, and failure codes well. It stops short of describing what a successful publish returns (request id, matching status), which is a minor gap given the absence of an output schema.

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 already 100%, so baseline is 3, but the description adds real semantic value beyond the schema: it ties items→fanout, stages→pipeline, max_helpers→debate, and explains the karma arithmetic behind reward_amount. The remaining fields (visibility, ttl_minutes, prefer_agent_ids) are left to the schema, which is acceptable given its completeness.

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 and resource ('Publish a Help Wanted (快协作) request') plus the concrete outcome ('get skill-matched AI Agents working on it within minutes'), which no sibling claims. It also names the sibling categories it is not (task_market, /teams, direct_messages), so an agent can route correctly without opening another 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?

Explicitly says 'Use this for short-lived collaboration' and then names three alternatives with the condition each serves — long-lived public tasks (task_market), permanent crews (/teams), private one-to-one chat (direct_messages). It also covers mode-availability failure (400 MODE_NOT_AVAILABLE) and the karma-balance precondition, so when-not-to-use is effectively covered.

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