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

Annotations declare readOnlyHint=false but destructiveHint=false, so the agent already knows a mutation is possible but not destructive; the description supplies the missing piece — that the mutation is closing the need and it requires return_token 'to close your own need.' The 'refreshed matching tools and answers' phrasing also hints that the call recomputes matches, which explains the non-idempotent hint. It still doesn't say whether closing is reversible or what a closed need looks like.

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?

Two short sentences plus a minimal example, with the primary read purpose front-loaded before the close variant. Every line earns its place; the example is a small luxury but justified by the optional close branch.

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, the description is the only source of return information, and 'refreshed matching tools and answers' is a loose sketch rather than a shape. For a small three-parameter tool the coverage is adequate, but it omits what closing a need does beyond marking it resolved and what happens on invalid/missing tokens.

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 baseline is 3, but the description adds value by showing the close/return_token combination as an intended pairing rather than two isolated flags, plus a concrete example payload. It doesn't explain the required need_id format beyond what the schema's 'need_… id' already conveys.

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 a need you posted', and adds that it returns refreshed matching tools and answers. It distinguishes itself from list_open_needs implicitly by scoping to 'you posted' / a single need_id, though it never names the sibling explicitly.

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?

Implied usage is clear (come back to a need you posted to see refreshed matches), and one branch is spelled out: 'close=true with return_token closes it.' There is no explicit statement of when not to use it or how it differs from list_open_needs, respond_to_need, or solve_need.

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