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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description goes further with real operational context: the checks performed (keys/owner/pause, exit route via NEAR Intents, holder concentration), the verdict decision rules, and the payment/auth model ($0.05/call over x402 on Base, prepaid x-credit-token header, 1 free call/day, no API key). Latency, caching, and failure modes are not covered, so it falls short of a 5.

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?

Purpose and action are front-loaded in the first clause, and the pricing sentence is clearly separated at the end. The middle section is a long em-dash run-on that bundles the three analysis dimensions and the verdict rules into one dense sentence, costing some readability.

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 no explanation, and the description still supplies inputs, default size, cost/auth model, and the decision thresholds for interpreting the verdict. For a two-parameter read-only gate this is everything an agent needs to call it and act on the answer.

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 100% for both parameters, and the description's notes ('size is in USD (default 100)', 'Required input: token') largely repeat what the schema already declares. Baseline 3 applies when the schema carries parameter semantics.

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 states a specific verb and resource ('One call before buying a NEAR token') and a concrete output ('GO / HOLD / STOP'), plus a precise scope: NEP-141 tokens on NEAR. It does not name or distinguish itself from adjacent siblings such as near_token_safety, near_agent_gate, or the generic pre_trade_gate, so an agent must infer the boundary.

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?

Usage context is explicit and front-loaded: run this before buying, with the trade size supplied in USD. The decision thresholds (15% loss / no route → STOP or HOLD; HIGH concentration → HOLD) tell the agent how to act on the result. No when-not guidance or named alternative is offered.

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