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

Annotations already cover readOnly/idempotent/openWorld, but the description adds genuinely useful behavior: the data is live from the NEAR RPC and priced by NEAR Intents, coverage is bounded ('tokens outside that list are not included'), and it reports how many tokens were scanned. It also discloses the payment/auth model ($0.02 per call over x402, x-credit-token header, 1 free call/day, no API key), which is material to invocation.

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 front-loaded with the core meaning (holdings + value) and the coverage caveat, then pricing last. The em-dash-heavy enumeration of tokens and the extended payment sentence are somewhat long but each clause carries real information, so waste is limited.

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?

An output schema exists, so return structure needn't be explained, and the description supplies the coverage limits, data sources, and input requirement an agent needs. It stops short of describing error/pagination behavior, but for a single-param, output-schema-backed tool it is essentially complete.

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?

There is a single parameter with 100% schema coverage, so the schema already documents 'account'. The description only restates that account is required and adds no format, syntax, or resolution semantics beyond the schema, making the baseline 3 appropriate.

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 a specific resource and scope: 'What a NEAR account holds, and what it is worth', enumerating NEAR (liquid and staked) plus NEP-141 token balances. An agent can tell this is a net-worth/portfolio tool for NEAR rather than a generic account lookup, but it never explicitly contrasts itself with close siblings like near_account, wallet_networth, or b20_portfolio.

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 states the required input ('Required input: account') and implies the use case (valuing a NEAR account's holdings), which is enough to know when to call it. However, it offers no explicit when-not guidance or alternatives, so routing against similar portfolio/wallet tools 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.