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

With no annotations, the description carries the full disclosure burden and does well: it reveals the answer's provenance (curated catalog validated against docs.near.org each sync, deprecation entries, forum threads, GitHub issues quoting the same error). It does not state what happens on an unmatched error or any rate/limit behavior, so it falls short of full transparency.

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?

Front-loaded with the verb and outcome before the source list, and every clause adds information about where the explanation comes from. The single long sentence is dense and slightly run-on, which costs it a point.

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 one-parameter, read-only lookup with no output schema, the description covers inputs, evidence sources, and the shape of the answer. It omits the fallback behavior when no catalog match exists, which is the main remaining gap for an error-lookup tool.

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 100% and the single parameter is self-documented, so the baseline is 3. The description earns above baseline by characterizing what counts as valid input (RPC responses, panics, CLI output) and stressing that the raw error text itself is required, which the schema's "as printed" note only partly conveys.

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 ("explain a NEAR error") plus the concrete payoff ("cause and fix"). The parenthetical enumerates accepted inputs (RPC response, transaction failure, contract panic, CLI output), which distinguishes it from siblings like check_code, find_known_issues, or semantic_search 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?

Usage is clear from the enumerated input types and the prerequisite "Needs the error text itself," making the trigger condition obvious. However, it never names an alternative tool or a when-not case (e.g., what to use when you only have a package name rather than error text).

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