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

Annotations already establish read-only/idempotent safety, so the bar is lower. The description goes beyond them with real behavior: login is required, an unbound conversation returns null, peerOpenNeeds is capped at 10, and an empty result must not be read as 'no 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?

Bracketed sections front-load the auth requirement, then behavior, then the call chain, with no filler. Dense but every clause earns its place.

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?

No output schema exists, and the description compensates by describing the return shape (null binding, <=10 peerOpenNeeds) and the interpretation caveat. Adequate for a single-param read tool.

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?

Single parameter (conversationId) with 100% schema description coverage, so the schema carries it. The description adds no syntax or format detail for the id, giving the baseline 3.

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: read the caller's conversation-level need binding/claim plus both parties' completion state. This is distinguishable from get_conversation (raw conversation) and get_my_needs (global needs), though it never names those siblings as contrasts.

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?

The 【组合链】line names the predecessor (list_my_conversations) and the downstream actions (send_message/complete_need), giving clear call context. It stops short of stating when-not to use it or which sibling to prefer.

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