get_latest_block

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 'Get the latest block.' It does not mention that it returns a block object, what fields are included, or that it supports multiple networks via the parameter. The behavior is implicitly a read operation, but no details are provided.

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 very concise, but it is under-specified and does not earn its place since it restates the name. It lacks necessary details that would make the description valuable, so while not verbose, it is not appropriately sized.

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 there is no output schema and no annotations, the one-sentence description is inadequate. It does not explain what the latest block contains, how to interpret the response, or mention the network parameter's role, leaving an agent with significant uncertainty.

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 description for the 'network' parameter is comprehensive (100% coverage), listing examples and default. The tool description adds nothing about parameters, but the schema already provides sufficient semantics, so the baseline of 3 applies.

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 'Get the latest block' is a direct restatement of the tool name 'get_latest_block', adding no new information. It does not distinguish the tool from sibling block-related tools or clarify the network scope, making it a tautology.

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 use this tool vs alternatives. No mention of preferred use cases, exclusions, or how it compares to tools like get_block_by_number or get_block_by_hash. The description provides zero usage direction.

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