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

With no annotations, the description carries the full behavioral burden. It does disclose one real behavioral fact — results are bounded to the latest blocks, not arbitrary history — and 'get' implies a read-only operation, but there is no statement on ordering, freshness/refresh semantics, or rate limits.

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?

A single front-loaded sentence with the resource first and the disambiguating examples in a compact parenthetical. Nothing is padded or repeated from the schema.

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 one-parameter read tool with no output schema, the description covers what the feed contains but not the shape of an event, the ordering, or how 'recent' is bounded in practice. It is adequate to invoke correctly, but not sufficient to set expectations about the response.

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% for the single 'limit' parameter (range 1–50, default 10), so the schema already does the work. The description adds nothing about the limit parameter, which is the expected baseline when coverage is complete.

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 names a concrete resource (on-chain activity) and narrows it with concrete event examples (mints / pack opens), so the agent knows exactly what comes back. No sibling covers activity feeds, so no differentiation is needed, which keeps this just short of a 5.

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?

Usage is implied by the scope phrase 'from the latest blocks' — an agent can infer this is the recency-limited feed and not a historical query tool. However, there is no explicit when-to-use or when-not-to-use statement, and no alternative is named (none of the siblings overlap).

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