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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real context beyond them — the data comes from OrbitWan's own node, and every program carries ok/complete/floors so unread or partial figures are not silently presented as zero. It does not mention auth, rate limits, ordering, or pagination.

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?

Three sentences, front-loaded with the resource and scope, then the integrity flags rule, then the unit convention. Dense but each sentence adds information; no filler or restatement of the title.

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 usefully pre-empts the biggest misreading of the results (partial/unread values masquerading as zero) and states that amounts are base-unit integer strings. The remaining gap is input-side: nothing about address format or what the response contains per program beyond principal and pending rewards.

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% for the single required 'address' parameter, so the description must carry the burden — but it only says the input is 'a Wanchain address' with no format expectation (hex 0x prefix, case, checksum) or validation behavior. The sentence about base-unit integer strings describes output magnitudes, not the parameter.

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 the resource precisely: 'Staking, farming, lending and deposit positions for a Wanchain address,' and enumerates the covered programs (xStake, PoS staking, Bridge staking, WanLend, XFlows farming). That scope separates it from broad siblings like get_address_summary or get_address_holdings, though it never explicitly contrasts itself with them.

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?

Applicability is implied by the enumerated program list ('across every program OrbitWan reads'), so an agent can infer this is the DeFi-position view rather than a holdings or activity view. There is no explicit when-to-use/when-not statement and no named alternative (e.g. get_address_holdings) to route against.

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