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

Annotations only declare idempotentHint=true and destructiveHint=false; the description goes well beyond that by disclosing the real side effect ('会真实开聊/发送'), the no-quota-limit fact, the crucial nuance that claiming is idempotent but the message is resent on every call, and the no-retry rule for 400/404/409/429. The idempotency nuance refines rather than contradicts the annotation, since it scopes idempotency to the claim and not the message.

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 login requirement and core action are front-loaded, and every clause carries information (side effect, quota, idempotency, error codes, workflow). The telegraphic semicolon/arrow style packs a lot into a small space but slightly reduces readability compared with plain prose.

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?

With no output schema and only two parameters, the description still covers prerequisites (login), side effects, quota, error-code handling, and the full upstream/downstream tool chain. An agent has everything needed to call it correctly and to know what to do afterwards.

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: that the ≤2000-char message is a real outbound first message that will be re-sent on every invocation even though the claim itself is idempotent. It also tells the agent to confirm the needId target before calling, which is behavioral rather than schema-level guidance.

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+resource: contact the author of an active ('在架') need and claim it ('联系在架需求作者并认领'). It distinguishes itself from siblings by naming the surrounding chain (get_need before, get_conversation_needs/send_message after, complete_need by both parties), so an agent can tell it apart from create_need, send_message, or start_conversation without opening any 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 an explicit invocation chain 'get_need→contact_need→get_conversation_needs/send_message→双方complete_need', and the error mapping '本人400' functions as a when-not (do not contact your own need). It also states the precondition '先确认对象' (confirm the target first) and the login requirement, leaving little to inference.

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