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

Goes well beyond the annotations: login required, LLM/money cost of full review, caching semantics, and interpretation of response fields (source=inferred is normal, placed/claimed states, warming-vs-empty, supply none/gated/warming). readOnlyHint=false is consistent with the disclosed resource spend, so no contradiction.

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?

Front-loads login and purpose, then packs routing/cost/field semantics into short bracketed clauses with zero filler. It is telegraphic and dense, which risks some readability, but every sentence carries distinct operational value.

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 mutation-flagged, output-schema-less tool, the description supplies the missing pieces: auth requirement, cost, caching, prerequisite tool, follow-up action, and decoding of return states. Nothing an agent needs to call it correctly is absent.

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 baseline is 3, but the description adds real meaning: metadataOnly=true avoids LLM spend while false returns member previews, and it clarifies the empty-subjectId default via the anchor-flow. It also references groupId/direction/profileVersion, which are not parameters here (routing hints), slightly muddying the mapping.

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: reading one's own/own-products' chain position plus upstream/downstream, anchored at any node per the title. It explicitly distinguishes itself from list_my_chain_anchors (get anchors first) and list_chain_group_members (combo chains), so an agent can route without opening schemas.

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?

Gives explicit sequencing ('先 list_my_chain_anchors 拿锚点'), a cost/side-effect tradeoff for metadataOnly, a 'don't repeat, it's cached' warning, an alternative tool for groupId/direction/profileVersion, and a follow-up route (placed=false → set_my_chain_position). When-to-use and what-to-do-next are both spelled out.

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