vechainstats_get_block_info

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

With no annotations, the description must disclose behavior, but it only says 'detailed information' without specifying what fields are returned, whether any permissions are needed, or any quirks. It adds minimal behavioral context beyond the tool name.

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 terse sentence with no filler, making it easy to parse. It could be more informative without sacrificing brevity, but as written it is well-structured and 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?

For a one-parameter lookup tool, the description conveys the core purpose, but it does not describe return values or usage context, and there is no output schema to fill the gap. This is adequate but leaves the agent uncertain about what 'detailed information' will be returned.

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?

The schema fully documents the single parameter blocknum as 'Block number' (100% coverage), so the baseline applies. The description adds no additional parameter semantics, but none are needed given the complete 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 identifies a clear action (get detailed information) and resource (a specific block), and the required blocknum parameter in the schema clarifies that it is block-number-based. However, it doesn't explicitly distinguish from sibling tools like get_block_by_timestamp or get_block_by_reference, leaving differentiation to the 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?

No guidance is provided about when to use this tool instead of alternatives. The description doesn't mention that it should be used when a block number is known or exclude the timestamp/reference variants.

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