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

Goes well beyond the annotations by explaining the underlying NEAR failure modes it protects against (mistyped accounts are unrecoverable; a token transfer silently fails unless the recipient has storage_deposit). It also discloses pricing ($0.02/call over x402 on Base), the x-credit-token prepaid path, a 1 free call/day allowance, and that no API key is needed — unusually rich operational context.

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 the core question ('will it clear, and is it safe?') before mechanism and pricing. It is somewhat long with several distinct clauses (safety framing, composition, failure modes, parameter usage, pricing, disclaimer), but each carries real information rather than filler.

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 an output schema present, return values need not be explained, and the description still covers purpose, triggering context, parameter usage, failure modes, and payment mechanics. Nothing material an agent needs to invoke it correctly 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?

Schema coverage is 100%, so the per-parameter descriptions already carry meaning and baseline is 3. The description adds relational semantics beyond the schema: token should be paired with amount for a token transfer, while near= is used for native-amount sizing, and it reiterates that 'to' is the only required input.

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 and resource — it evaluates whether a NEAR payment will clear and is safe, returning GO/HOLD/STOP before an agent sends. It explicitly positions itself as 'the NEAR counterpart of agent-pay-gate' and names the two things it composes (account posture + NEP-141 transfer preflight), which distinguishes it from siblings like near_transfer_preflight and 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?

Gives a clear triggering context ('Before you pay a NEAR account') and mode selection ('Pass token (+amount) for a token transfer, near= for native-amount sizing'). It does not name explicit alternatives or a when-not-to-use, but the counterpart framing plus mode guidance leaves little ambiguity.

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