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

Beyond the idempotentHint/destructiveHint annotations, it discloses login requirement, 400 on invalid cursor, 409 on profileVersion change with the correct recovery (re-read anchor), per-page LLM cost, and the meaning of an empty 'warming' page and total=null. That is substantial operational context the annotations do not carry.

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?

Very short and front-loaded with the prerequisite and pagination contract, with no filler sentences. The telegraphic semicolon style ('warming空非无人，total=null未知非页长') packs several ideas per clause and is dense but not wasteful.

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 six parameters, no output schema, and a paginated flow, the description covers prerequisites, error recovery, cost constraints, and even response-field semantics (supply states, total=null, warming). It stops short of describing member record contents or payload shape, but for a list tool it is otherwise sufficient.

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 100%, so the schema already documents limit, cursor, groupId, direction, subjectId and subjectType. The description only reinforces that the cursor is a signed token to pass unchanged and implicitly ties groupId/direction to get_chain_anchor's output; it introduces no new parameter-level detail worth more than 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 jumps straight into pagination mechanics ('按get_chain_anchor返回groupId/direction/profileVersion分页') rather than stating plainly that this lists the members of one upstream/downstream chain ring. The workflow hint 'anchor→成员页→get_creator' and the mention of 'supply' let an agent infer the resource, but the verb+resource is only implicit and the title carries most of the load.

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 names the prerequisite sibling (get_chain_anchor) that supplies groupId/direction, warns against exhaustive enumeration due to per-page LLM cost, and forbids retrying with the same params after a 409. It also points forward to get_creator. No explicit exclusion against alternatives such as list_my_chain_anchors, but the sequencing guidance is clear.

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