NEAR MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool imports an account but doesn't describe what 'import' entails (e.g., whether it overwrites existing accounts, requires specific permissions, or has side effects like storing sensitive data locally). It mentions network suffixes but doesn't explain behavioral implications (e.g., mainnet vs testnet usage). For a mutation tool with zero annotation coverage, this is insufficient.

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 appropriately concise with three sentences. The first sentence states the core purpose, the second explains the benefit, and the third provides network-specific formatting details. It's front-loaded with the main action, though the network suffix note could be integrated more smoothly.

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 complexity (mutation with nested input schema for two import methods), lack of annotations, and no output schema, the description is incomplete. It doesn't cover parameter details, behavioral traits (e.g., security implications of importing private keys), or expected outcomes. For a tool that modifies local keystore state, this leaves significant gaps for an AI agent.

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 0%, so the description must compensate. It adds some context by mentioning network suffixes (.near for mainnet, .testnet for testnet), which relates to the 'networkId' parameter and 'accountId' format. However, it doesn't explain the two import methods (from private key vs file) or their parameters (e.g., 'privateKey', 'filePath'), leaving key semantics undocumented. Baseline is 3 due to partial compensation.

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 action ('import an account') and the target ('into the local keystore'), with the purpose being to enable use of the account with other tools. It distinguishes from siblings like 'account_create_account' (creation vs import) and 'system_remove_local_account' (import vs removal), but could be more explicit about differentiation from 'account_export_account' (export vs import).

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 provides minimal guidance on when to use this tool, mentioning only that imported accounts can be used with other tools. It lacks explicit when-to-use scenarios, prerequisites (e.g., needing a private key or file), or alternatives (e.g., using 'account_create_account' for new accounts instead). No exclusions or comparisons to siblings are provided.

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