get_events_of_latest_block

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds useful behavioral details like skipping empty blocks, page size limits, and indexing lag. It doesn't disclose exact page size or pagination method, but the advisory about limits is valuable.

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?

Three concise sentences front-load the purpose, then state limitations and alternative, with no redundant words or repetition of schema content.

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?

No output schema exists, but the description effectively covers return limitations (page size, indexing lag) and points to the sibling for precise control. It could mention event structure or pagination handling, but is largely sufficient for a simple read tool.

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?

Schema description coverage is 100%, so both parameters (network, onlyConfirmed) are well-documented. The description adds no extra parameter-specific semantics, which is acceptable given the schema handles it.

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 events from the most recent non-empty block, emphasizing it skips empty blocks. This distinguishes it from siblings like get_events_by_block_number and get_events_by_transaction_id.

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?

It explicitly mentions limitations (default page size, indexing lag) and recommends get_events_by_block_number for precise control with pagination, providing a clear alternative and when to use it.

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