NOVAI block by height or hash

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

No annotations provided, so the description carries the burden. It discloses that the endpoint retains a bounded recent window for height lookups and that hash lookups work for any indexed node. It does not explicitly state read-only nature or authentication needs, but the 'get' action implies no side effects. Adequate but not comprehensive beyond the given limitations.

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?

Three sentences with no wasted words. The most critical information (parameter rule, return contents, and caveats) is front-loaded and efficiently presented. Perfectly concise.

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?

Despite no output schema, the description fully enumerates return fields (height, hash, parent hash, round, state root, transaction count) and explains the null case. It covers both parameter modes and their limitations, leaving no ambiguity for a single block fetch 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 description coverage is 100%, so the description's contribution is limited. The description repeats the mutual exclusivity and adds the behavioral context about lookup limitations, providing some value beyond the schema. Baseline of 3 is appropriate as the schema already documents parameter meanings.

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 name and title clearly indicate a block fetch by height or hash. The description specifies a verb ('Fetch') and resource ('single committed block'), distinguishing it from sibling tools like 'get_transaction' by resource type. However, no explicit sibling differentiation is provided.

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 states 'Provide exactly one of height or hash' and explains the limitation that very old heights return null, guiding when to use which parameter. It does not explicitly mention when not to use this tool or compare to alternatives, but the context is clear for the intended use.

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