dero_get_last_block_header

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by specifying the tool returns only the header (not full block body) and outlines the output structure. It does not contradict annotations and provides context beyond what annotations alone offer.

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 extremely concise, consisting of three short sentences. It front-loads the core action ('Get the header of the current tip block') and provides structured guidance on usage and output. Every sentence serves a purpose without redundancy.

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 simplicity (no parameters, no output schema), the description fully covers purpose, usage context, and expected output format. It mentions the output structure ({ block_header: { hash, height, ... } }) which compensates for the lack of an output schema. No further information is needed.

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 tool has zero parameters. With schema coverage at 100% (empty schema), the description correctly provides no parameter details. Per guidelines, the baseline for 0 param tools is 4, and the description meets this standard by not requiring additional parameter explanation.

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 retrieves the header of the current tip block, specifying 'no full block body'. It uses specific verbs ('Get the header') and resource ('current tip block'). This distinguishes it from siblings like dero_get_block which return full block data.

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?

Explicitly states when to call: 'when you need tip block metadata without the transactions or miner_tx payload'. It also names an alternative: 'PREFER dero_get_block when you need transactions or the miner_tx'. This provides clear guidance on tool selection.

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