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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so the safety profile is covered. The description adds non-obvious behavioral context the annotations cannot: the node serves the tip only and historical blocks are closed/unavailable, which changes how an agent should behave on failure. It does not discuss freshness windows, rate limits, or error semantics, so it stops short of a 5.

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-loaded with the resource, then the use/don't-use routing, then the return fields - a clean information hierarchy with no filler sentences. The dense comma-separated field lists are justified by the absence of an output schema, though it reads slightly list-heavy.

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 carries the return-value burden and does so by naming the returned fields explicitly. The tip-only limitation is called out, so an agent knows both what it gets and what it cannot get.

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 and the description correctly documents no inputs, so there is nothing to disambiguate. Baseline for a no-parameter tool is 4.

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+resource (current/tip TRON block) and enumerates exactly what it carries: number, id, parent, timestamp, tx count by contract type, and producing witness. It also implicitly separates itself from tron_get_block by framing this as the tip-only read.

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?

Contains explicit 'When to use' (how busy TRON is now, what is in the block being produced, who produced it) and 'Do not use' (fetching older blocks - the lite full node serves the tip only). This is exactly the when/when-not guidance that routes an agent away from tron_get_block.

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