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

With annotations already covering readOnly/idempotent/destructive, the description goes well beyond them: it discloses the methodology (counting full-access keys that can redeploy, querying owner and pause switch), the verdict mapping, the data returned, the live NEAR RPC source, and the payment model ($0.02/call via x402 on Base, prepaid x-credit-token header, 1 free call/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?

The decision question and GO/HOLD/STOP mapping are front-loaded and high-value. The pricing/auth sentence is long and slightly crowds the behavioral content, but nearly every clause carries information an agent needs.

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?

For a single-parameter read tool with an output schema, the description is complete: trigger, methodology, verdict semantics, data scope, and the payment/auth path are all covered. Nothing needed to call 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 description coverage is 100% with a single 'token' parameter, so the schema already carries the semantics. The description only restates 'Required input: token' and adds no format or syntax detail, so the baseline 3 applies.

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 — assessing who can change a NEAR NEP-141 token's contract — and immediately frames the output as a GO/HOLD/STOP verdict. An agent can distinguish it from near_pre_trade_gate or token_risk 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?

Explicitly scopes usage: 'Before an agent takes a NEP-141 token on NEAR: who can change it?' gives a clear trigger condition. It does not name alternative sibling tools for adjacent questions (e.g. holders or liquidity), so it stops short of full when/when-not routing.

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