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

Adds real value beyond annotations by stating '只读，不接单或付款' (read-only, does not accept orders or pay), which explicitly separates it from claim/quote/payment siblings. It also clarifies pricing field semantics. Annotations only cover idempotent/destructive, so this extra context is useful.

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?

Short, front-loaded, and no filler. The terse phrasing ('不端算分账') is somewhat cryptic but the structure is 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?

No output schema and zero param documentation in the schema, so the description carries the burden. It covers the read-only/accept-payment exclusion and mine semantics but leaves query and pagination parameters undocumented, which is a meaningful gap for a list tool.

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 0% with 3 undocumented params; the description clarifies the 'mine' scope and pricing semantics but leaves 'q' and 'limit' entirely unexplained, so it only partially compensates.

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+resource: '查看人脉悬赏或本人全部悬赏' (view network bounties or all of one's own bounties). This clearly distinguishes it from claim_network_bounty, publish_network_bounty, and manage_network_bounty, though it doesn't explicitly contrast with the sibling get_network_bounty.

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?

Provides a login prerequisite ('登录') and notes the mine scope, but does not say when to choose this list over get_network_bounty or preview_network_bounty_price. Usage is implied rather than explicit.

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