check_balance

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.