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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and an output schema exists, so the safety profile is covered. The description adds no behavioral context of its own — no note on network scope, freshness/latency of the tip, or failure modes — beyond pointing at external docs.

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?

It is very short with no filler, but it is structured as a docs link followed by a raw REST path rather than as a front-loaded statement of what the agent gets back. The first line is a bare URL that conveys nothing on its own.

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 zero-parameter read with an output schema, the minimum needed to invoke it is present. Still, the description never says in words that the return value is the tip block hash, nor distinguishes it from the sibling height tool, leaving the agent to lean entirely on the name and external documentation.

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 takes zero parameters, so the baseline is 4; there is nothing for the description to explain. The empty schema is consistent with the described parameterless GET endpoint.

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 only restates the tool name as a REST path ('GET /api/blocks/tip/hash'), which an agent can decode to mean 'the hash of the current chain tip'. That is enough to grasp the resource, but it offers no plain-language statement and no differentiation from close siblings like get_block_tip_height or get_block_hash_by_height.

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?

There is no guidance on when to call this versus get_block_tip_height, get_block_hash_by_height, or get_block. The agent must infer usage purely from the name and URL path, with no exclusions or alternative routing.

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