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

The annotations only say idempotent and non-destructive; the description consistently adds real behavior: it is read-only, requires login, returns only actually-settled amounts plus the five original-order pricing amounts, legacy orders keep their original terms, and no withdrawal is possible. Those are meaningful scope and auth details beyond the annotations, though the return shape remains undescribed.

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 extremely short, but the semicolon-separated fragments are not front-loaded around a clear subject and read like compressed internal notes rather than an agent-facing statement. Nothing is padded, yet the phrasing is cryptic rather than efficient.

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 parameters and no output schema, the description carries the full burden of explaining what comes back, and it only vaguely alludes to 'five pricing amounts' without naming them or describing the response. For a zero-arg data-retrieval tool this leaves an agent guessing at the returned content.

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 tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate at the input level.

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 '只读实际结算及原单pricing五项金额' implies a read-only lookup of settlement/pricing amounts for the caller's own referral earnings, which roughly matches the title. However, the description never states the verb+resource plainly ('view my referral earnings') and is written as telegraphic clause fragments, so an agent must infer the purpose from the title.

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?

'不提现' does give one useful negative constraint: this tool is not for withdrawals. '登录' signals a login prerequisite. Beyond that there is no guidance on when to call this versus sibling tools such as get_network_payment_status or list_network_bounties, and no alternatives are named.

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