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

Annotations already declare readOnly/openWorld/idempotent/destructive=false, so the safety profile is covered. The description adds meaningful context beyond them: the data is 'Live from the NEAR RPC,' and it surfaces derived flags (single-key wallet, key-replaceable contract, un-signable account) plus pricing/access terms (x402 $0.01, prepaid header, 1 free/day, no API key).

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?

Well front-loaded: purpose question first, capability enumeration second, then operational/pricing terms last. The pricing and free-tier sentences are somewhat verbose, but for a metered x402 tool that access information is load-bearing, and no sentence is redundant with the schema.

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?

Given an output schema exists (so return shape needn't be described), the description still covers what data is gathered, the source of truth (NEAR RPC), the notable derived flags, and the billing/access model. Nothing an agent needs to decide whether and how to call this is missing.

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?

Only one parameter, with 100% schema description coverage ('NEAR account'). The description merely restates 'Required input: account' without adding format, resolution, or validation semantics beyond what the schema already conveys, matching the baseline 3 for a fully-covered single 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 opening question states a specific resource ('NEAR account') and its scope ('who controls it'), then enumerates exactly what is returned: existence, kind (named/implicit/0x), balance breakdown, contract/token status, and controlling keys. An agent can distinguish this account-identity/ownership tool from siblings like near_account_age or near_token_safety without opening any schema.

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?

'Before an agent pays or trusts a NEAR account' gives a clear triggering context for use. It does not, however, name alternative or adjacent sibling tools (e.g. near_account_age, near_wallet_activity) so the agent gets positive context but no explicit exclusions or routing.

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