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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that events are indexed and paginated, but it does not explain ordering defaults, cursor behavior, or result shape beyond what annotations provide.

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 a single, front-loaded sentence with no filler. Its brevity is appropriate, though it leaves several parameters unexplained.

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 8 optional parameters, low schema coverage, and no output schema, the description is too thin to fully prepare an agent to call the tool correctly. It does not explain pagination mechanics, ordering, block-range filtering, or cursor semantics.

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 only 25%, so most of the 8 parameters are not documented in the schema. The description says "filterable and paginated" but does not explain limit, order, cursor, account, fromBlock/toBlock, or what the type parameter accepts beyond the schema's own list.

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 states a specific resource (indexed events) with concrete event examples and notes filtering/pagination. It is clear what the tool returns, though it does not explicitly distinguish this read tool from the many sibling tools, most of which are unrelated get_/prepare_ operations.

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?

The phrase "filterable and paginated" implies that this is a list/query tool, but there is no explicit guidance on when to use it versus alternatives, nor any when-not conditions. Usage is inferable but not spelled out.

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