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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds state constraints ('已兑换', '仍有效', '冻结分享'), which is useful behavioral context beyond the annotation. It still omits authorization details, error behavior for invalid states, and what is actually returned.

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 short, but it is a verbless fragment that does not front-load the action. Brevity is achieved through under-specification rather than efficient communication, leaving the agent to infer the purpose from the title and name.

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?

Given the dense sibling set around cooperation shares and the lack of an output schema, the description is too incomplete. It neither explains what the tool returns nor gives the parameter meaning, and it cannot fully compensate for the absence of schema descriptions.

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 description coverage is 0% and there is one required parameter, 'id', which the description never mentions. It does not clarify whether the id refers to a cooperation share, a frozen share record, or some other object, nor does it add format or lookup semantics beyond the schema's type and length constraints.

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 does not state what action the tool performs; it only gives a condition ('仅本人已兑换且仍有效的冻结分享'). The title and name imply reading a cooperation share access, but the description itself does not say it retrieves or reads anything, and it does not distinguish itself from siblings like preview_cooperation_share, list_cooperation_shares, or redeem_cooperation_share.

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 communicates a meaningful precondition: only the caller's own redeemed and still-valid frozen share is accessible. However, it does not say when to use this tool instead of preview_cooperation_share or list_cooperation_shares, nor does it mention what happens for expired or unredeemed shares.

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