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

Annotations declare idempotentHint and destructiveHint=false but notably omit readOnlyHint, so the explicit '只读' claim adds real value. It also discloses two things annotations cannot: authentication is required, and the call does not run global expiry/refund jobs — useful side-effect information. Return-shape detail (pagination, ordering) is absent.

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-only scope, but the semicolon-delimited fragments are telegraphic rather than well-formed sentences, and '不运行全局到期/退款' reads as an internal implementation note. Nothing is padded, yet the compression costs readability.

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 output schema, the description correctly clarifies what is not returned (contact details) and what side effects do not occur. For a two-parameter list tool it is close to sufficient, but the missing pagination/limit semantics leave a real gap for an agent deciding how to page through results.

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%, so the description must carry the burden. It partially does: '本人发起/参与' maps onto the box enum values requested/participating, which is a genuine semantic hint. However the limit parameter (1-100, default 20) and any pagination behavior are entirely undocumented in both schema and description.

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 states the resource and scope clearly: read-only listing of introductions the caller initiated or participates in, plus original-order pricing. It is distinguishable from get_network_introduction (single record) and manage_network_introduction (mutation), though the listing verb itself is only implied by the tool name rather than stated.

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 implies when this is appropriate (read-only view of one's own introductions) and rules out contact-detail retrieval, but never names the alternatives an agent should pick instead — get_network_introduction for a single record or manage_network_introduction for accept/decline actions. The routing decision is left to inference.

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