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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds the behavioral constraint that only redeemed and still-valid shares are accessible, which is useful context but does not explain what happens for invalid/expired shares (e.g., empty response or error). It adds some value beyond annotations but leaves ambiguity.

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 description is extremely short (one clause) and front-loads the constraint, but it is cryptic and lacks an explicit verb or resource. It is concise but under-specified, offering minimal structural benefit.

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 simple tool with one parameter and no output schema, the description should explain what is returned and error conditions. It only states a scope constraint, leaving the agent to infer the purpose and outcome. Annotations cover safety, but the description is insufficient for correct invocation.

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?

The schema has one required 'id' parameter with no description (0% coverage). The tool description does not mention 'id' at all, so there is no added meaning about what the ID represents, its format, or how it relates to the share. With zero schema coverage, the description should compensate but does not.

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 title indicates 'read opened sharing scheme', and the description specifies a constraint (only redeemed, valid, frozen shares) but does not clearly state what the tool returns or that it retrieves a share access by ID. It is distinguishable from list_cooperation_shares and redeem_cooperation_share only through the constraint, not an explicit purpose statement.

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?

No guidance on when to use this tool vs alternatives. It does not mention that list_cooperation_shares lists all shares, or that redeem_cooperation_share is for redeeming. The constraint implies it is for already-redeemed shares, but no explicit usage context or exclusions are given.

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