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

The only annotation is destructiveHint=false, so the description carries the real disclosure burden and does: it declares login requirement, states it is NOT read-only (每条真实LLM并记录曝光), warns results are truncated beyond the cap, and notes contact info is excluded. 'Non-read-only' is compatible with destructiveHint=false, since an LLM-run exposure-recording call is a side effect but not a destructive one.

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?

It is dense but fully front-loaded: login gate, then what is returned, then cost/side-effect warning, then the truncation and alternative, then the follow-up chain. Each clause carries distinct information (auth, cost, limits, routing) with no 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 two-parameter tool with no output schema, the description covers auth, per-item cost and side effects, truncation behavior, missing pagination, exclusion of contact data, the correct alternative for depth, and the downstream handoff. Nothing an agent needs in order to call it correctly or avoid misusing it is missing.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: it clarifies that only 5 needs are actually run per call while extras are merely listed, resolving the apparent conflict with the schema's maxItems=20. It does not add anything about limitPerNeed beyond the schema default.

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 states a specific verb (聚合 aggregate) plus resource (本人 OPEN 需求的人选及 matchedNeeds) and bounds the scope to at most 5 open needs. It explicitly contrasts itself with get_need_recommendations, so an agent can tell the batch view from the single-need deep view without opening either 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?

It gives when-to-use (aggregate my open needs), when-not-to (single-need deep read → get_need_recommendations), and an operational warning not to poll because there is no cursor. It also spells out the follow-up path get_creator → start_conversation/contact_need, which is exactly the routing an agent needs.

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