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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, and the description states 需要登录, which is beyond what annotations provide. It also discloses boundary behavior (conversationNeed=null when unbound, peerOpenNeeds capped at 10). It does not detail pagination or ordering of peerOpenNeeds, which prevents a 5, but the combination of auth note + null case + cap is strong.

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?

The description is dense but well-structured: a headline result, a bullet-like enumeration of payloads, a null case, a chain, and a scope restriction. Every sentence earns its place and the critical usage context is front-loaded.

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 tool with one fully documented parameter and no output schema, the description covers the main usage context, auth requirement, return highlights, and integration with send_message/complete_need. Missing an explicit note that the response contains both fields even when peerOpenNeeds is empty, and no details about sorting, but these are minor given the richness already present.

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 schema fully documents conversationId; the description reinforces that it is the id from list_my_conversations and implies it must be a conversation the user participates in. That adds a validity condition beyond the schema's one-line field description.

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 a specific verb ('查'), a precise resource ('会话的需求上下文'), and immediately enumerates the two return payloads (conversationNeed and peerOpenNeeds) with their relevant fields. It also contrasts with siblings like get_conversation and list_my_conversations by stating exactly what layered context it adds.

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 an explicit combination chain: list_my_conversations → this tool → send_message / complete_need, tells conditions (only own conversations), and says what to use it for ('判断能否/是否该 complete_need', '找合作切入点'). It also preempts misuse by noting it cannot query other people's conversations.

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