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

Beyond the single destructiveHint:false annotation, the description discloses login/auth requirement, a scope restriction (own needs only), an error contract (do not retry not_your_need), the response content (match score, reason, author need), and pagination behavior (cursor carries seen IDs; don't refresh from page one). That is exactly the behavioral context annotations cannot supply.

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?

Semicolon-delimited clauses pack a lot of value with no filler, and the workflow chain is front-loaded. The very terse telegraphic style ('登录;仅本人需求,not_your_need勿重试') slightly hurts readability and puts the login note ahead of the purpose.

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 4-parameter read tool with no output schema, the description covers auth, scope, return content, error handling, and pagination — most of what an agent needs. A clearer statement of how it differs from get_my_need_matches would complete it.

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; the description still adds meaning by explaining that cursor carries already-seen IDs and that the seen list soft-demotes on continuation, plus that needId must be one of my own. This goes beyond the schema's own wording for cursor/pagination.

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 resource and output: it returns recommendations of who can satisfy my need, including match score/reason and the author's need. This is far more than restating the name. The one gap is that it doesn't distinguish itself from the near-identical sibling get_my_need_matches (nor search_needs/find_customer_needs), so an agent must still infer which recommender to pick.

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 lays out an explicit workflow chain: list_my_needs → recommendations → get_creator → start_conversation/contact_need, which tells the agent both preconditions and next steps. It also says not to retry on a not_your_need error. What's missing is an explicit exclusion against the sibling match/feed tools.

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