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

Annotations already declare readOnlyHint=true, but the description adds behavior that the annotation does not: a login is required, the result is null when no binding exists, peerOpenNeeds is capped at 10 items, and an empty result must not be read as 'no needs'. Those are real operational caveats not present in structured fields.

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 compact and front-loaded, with every clause carrying content (auth, return semantics, cap, caveat, workflow). The telegraphic semicolon style is efficient but somewhat hard to parse, which keeps it from a 5.

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?

There is no output schema, and the description does cover the key return facts (null on no binding, 10-item cap on peerOpenNeeds) plus the interpretation caveat. The fuller shape of '双方完成态' is left implicit, but for a one-parameter read tool this is close to complete.

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% for the single conversationId parameter, and the description adds only the ownership scoping ('本人会话'), which is a modest addition. It adds no format or lookup hints beyond what the schema already supplies, so the baseline of 3 fits.

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 read operation: it reads the current user's conversation-bound claims and both parties' completion state. This distinguishes it from get_conversation and get_conversation_members, which cover different aspects of a conversation. The phrase '需求上下文' is dense, but the body clarifies what the returned data is.

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 workflow 'list_my_conversations → 本工具 → send_message/complete_need' explicitly places the tool between listing conversations and messaging or completing needs, so the agent can tell the agent when to reach for it. It does not name an exclusion case or a true alternative, which keeps it short of a 5.

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