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

Annotations only supply idempotentHint=true and destructiveHint=false, so credit goes to the description for adding the login requirement, the ownership and OPEN-status preconditions, the 403/409 error semantics with 'don't retry' advice, and the note that claim completion does not change need status. What is missing is partial-update behavior for omitted fields and any note on validation failures for title/detail.

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?

Very compact and front-loaded with the login precondition, and every fragment carries information (no filler). The telegraphic semicolon style makes it harder to parse than a couple of short sentences would, which is the only real conciseness/structure cost.

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 5-parameter mutation tool with no output schema, the description covers auth, ownership, status preconditions, error handling, and the surrounding workflow. It does not close the loop on partial-update semantics for the four optional fields, which is the main remaining gap.

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 only 40%: type's enum is richly documented in the schema and needId carries a description, but title, detail, and images have no descriptions at all. The description adds only the provenance of needId (from list_my_needs) and the implicit PATCH/partial-update semantics; it says nothing about length limits, image count, or what happens to fields left out.

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 fragment 'patch本人OPEN需求' names a specific verb (patch/update) plus resource (need) plus scope (own, OPEN-only), which separates it from create_need, delete_need, cancel_need, complete_need, and reopen_need. It stops short of naming any of those siblings explicitly, so the differentiation is inferred rather than stated.

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?

Usage is stated through preconditions and an explicit workflow chain: list_my_needs to obtain the id, then confirm, then update_need, then get_need. The exclusions are encoded as error cases (403 non-owner, 409 already closed) rather than as a when-not-to-use statement, but together they give an agent clear routing guidance.

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