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

Annotations are absent, so the description must disclose behavioral traits. It mentions 'via JSON-RPC' indicating a network call, but lacks details about error handling, return format, side effects (e.g., read-only), or what 'key stats' entails. This is insufficient for a network-touching tool.

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 a single, concise sentence that front-loads the core purpose. It contains no filler and is easily scannable, earning full marks for conciseness.

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 has three parameters, no output schema, and no annotations, the description is minimal. It fails to explain the 'key stats' it retrieves, the meaning of network options, or how results are returned. This is insufficient for an agent to use the tool confidently, especially with no output schema to infer return structure.

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 only 33% (only rpc_url has a description), and the tool description does not explain any parameters. It does not compensate for the low schema coverage; account_id, network, and rpc_url are not clarified semantically beyond their names. The description adds no parameter-specific value.

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 clearly states the tool's function: 'Check NEAR account balance and key stats via JSON-RPC.' It specifies the action (check) on a specific resource (NEAR account balance) and distinguishes it from siblings like create_wallet and sign_transaction, which serve different purposes.

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?

The description does not provide any guidance on when to use this tool versus alternatives. It only states what it does without context for selection criteria, prerequisites, or exclusions. Siblings are unrelated, but no explicit usage instructions are given.

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

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

No annotations are provided, so the description carries the burden. It says 'Create or import' which implies mutation, but it doesn't disclose side effects like whether it stores the wallet, how private keys are handled, or if it returns the keypair. It adds the 'implicit account info' detail, but misses specifics like network selection behavior or privacy implications.

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?

Single sentence, concise, and to the point. No fluff. Perfectly sized for the purpose.

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 4 parameters, no output schema, and no annotations, the description is somewhat incomplete. It doesn't explain what 'implicit account info' returns, how network affects the wallet, or the implications of include_private_key. However, the tool is relatively simple, and the description covers the core action. It's adequate but leaves gaps.

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 50%, with descriptions on account_id and private_key, but network and include_private_key lack descriptions. The description mentions 'Create or import' which covers the private_key parameter, but doesn't clarify network or include_private_key. With 50% coverage, the description should compensate more, but it adds minimal semantic value beyond the schema.

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 clearly states the tool creates or imports a NEAR wallet (keypair), which is specific and distinguishes it from sibling tools like check_balance and sign_transaction. However, it doesn't mention the 'include_private_key' behavior or 'implicit account info' details, but the core purpose is clear.

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?

The description implies when to use: when you need to create or import a wallet. But it doesn't provide explicit guidance on when not to use it or alternatives; relying on sibling names, it's clear this is for wallet creation, not balance checks or signing. Adequate but not explicit.

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

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

With no annotations present, the description must disclose behavioral traits itself. It tells us it signs and uses an ED25519 key, but it omits what is returned, whether this is an offline/side-effect-free operation, or how the private key is expected to be formatted/handled. This is incomplete for an unannotated signing tool.

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 entire description is a single, packed sentence with no fluff. Main action, resource, action types, and signing algorithm are all front-loaded.

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 six required parameters, no annotations, low schema coverage, and no output schema, this one-line description underspecifies the context. An agent still needs to infer the data format for signer_private_key, nonce, recent_block_hash, and knowledge of the signing response, so the description is insufficient for the tool's complexity.

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 only 17%, so the description needs to compensate for the remaining parameters. It adds the ED25519 key detail and names transfer/function_call actions, but it does not clarify signer_id, receiver_id, nonce, recent_block_hash format, or the action object construction beyond what the schema's type structure already exposes.

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 clearly identifies the primary verb and resource: 'Sign a NEAR transaction payload' and specifies the action types and algorithm. It distinguishes itself from sibling tools (create_wallet, check_balance) as the transaction signing operation.

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 is implied by the description: when a NEAR transaction payload needs to be signed. However, there is no explicit wording about when to prefer or avoid this tool, nor any prerequisites like needing a nonce/recent block hash from the chain, so it stops at an implied-level of guidance.

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