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

Annotations only declare idempotentHint and destructiveHint=false, so the description carries real added weight: it discloses that login is required, that visibility is permission-scoped ('有权查看的'), and that the call performs no order acceptance or payment. That is meaningful beyond the structured fields, though the discount business rule is stated too cryptically to act on.

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 and front-loads the read intent, but the semicolon-separated fragments and the unexplained '新优惠实付不能套旧30%' rule read as clipped internal notes rather than a clear structure. Tight, but at the cost of intelligibility.

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 one-parameter read tool with no output schema, the description does indicate what is returned (bounty, original-order pricing, funding quota) and states auth/permission requirements. It still leaves the id semantics and the role of the discount rule unclear, so it is adequate but not fully complete.

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 the single required 'id' parameter is never explained in the description; an agent must infer from the tool name that it is a bounty identifier. With full burden on the description and nothing added about format or scope of the id, this falls below the baseline.

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 names a specific verb (读取/read) and concrete resource content (悬赏、原单pricing、资金名额), so an agent knows this returns a bounty's terms and pricing rather than mutating anything. It does not differentiate itself from nearby siblings like preview_network_bounty_price, quote_network_bounty, or list_network_bounties, and the final fragment about the old 30% discount adds noise to the stated purpose.

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?

The opening '登录' implies an authentication precondition, and '不接单或付款' usefully signals this is a read/view step rather than the accept-or-pay action, which implicitly steers away from claim_network_bounty or payment tools. However, it never names an alternative tool or states explicit when-to-use conditions, so routing must be inferred.

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