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

Annotations already declare readOnly/idempotent/openWorld, and the description goes well beyond them: it enumerates return fields and the null-missing convention, states typical latency (0.2-1 s), discloses the pricing and the shared 10-read daily IP quota, and warns that returned page/on-chain strings are untrusted. That is unusually rich behavioral context for a read tool.

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-loads purpose and input before returns, latency, cost, and the safety warning. Dense but every sentence carries information; the pricing/free-pool sentence is the longest and only marginally relevant to invocation correctness.

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?

With no output schema, the description correctly enumerates the returned fields and the null-for-missing rule, and it covers cost, quota, and injection handling. Nothing an agent needs to call this one-parameter read tool is missing.

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?

Only one parameter with 100% schema description coverage and an explicit enum, so the schema fully carries parameter meaning. The description restates the enum values but adds no syntax or format detail beyond them, which is the baseline-3 case.

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 ('read the latest block header') and scopes it to two named chains. The word 'latest' implicitly distinguishes it from the sibling get_block_at_time, which handles historical blocks.

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?

Names the accepted chain values and gives operational context (latency, cost, free-quota pool shared with the sanctions screen and URL check), which helps an agent budget calls. It never explicitly states when to prefer get_block over get_block_at_time or get_gas, so routing vs siblings is left to inference.

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