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

Beyond the read-only and idempotent hints, the description adds significant behavioral context: it is 'Live from the NEAR RPC' (network dependency), costs $0.01 per call with 1 free call/day, requires no wallet or API key, and catches an edge case like sending to the token contract itself. It also pre-announces the GO/HOLD/STOP output style and the explicit fix with NEAR cost.

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?

The description is longer than average but every sentence earns its place: core purpose, checks, fix output, optional-input behavior, edge case, live RPC, required inputs, pricing, and auth. It is front-loaded with the primary question and uses compact punctuation to convey dense context without fluff.

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 the tool's moderate complexity, the description gives an agent everything needed to invoke it correctly: required and optional inputs with their semantics, what checks are performed, the output style, live RPC behavior, and cost/auth details. Since an output schema exists, omitting a detailed return-structure explanation is acceptable.

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% with basic parameter descriptions, so the baseline is 3. The description adds meaning by explicitly marking token/to as required and explaining that supplying from and amount enables an additional sender-balance check. It does not add format details for token or to, but the schema already covers those.

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 opens with a concrete question — 'Will this NEAR token transfer go through?' — and enumerates specific checks: token real/not paused, receiver exists, registration/storage_deposit, sender balance, and sending to the token contract itself. This scopes the tool clearly to NEP-141 transfer preflight, distinguishing it from generic safety tools like safe_to_send or near_pre_trade_gate.

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 condition for use: 'Before sending a NEP-141 token on NEAR', and identifies required inputs (token, to) plus optional extensions (from, amount). It does not explicitly name sibling alternatives or state when not to use it, so it only reaches a clear-context level rather than full when/when-not guidance.

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