get_approval_events

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

There are no annotations, so the description carries the burden of disclosing behavioral traits. It only states 'Get ERC20 approval events', which is obvious from the name, and does not mention read-only nature, pagination, ordering, return format, or default block ranges. This is insufficient for a tool with no annotation support.

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, concise sentence that directly conveys the core function with no redundant information. It is appropriately front-loaded and contains zero filler.

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 six mandatory optional parameters and no output schema, the description is far too terse. It does not explain the structure of an approval event (e.g., owner, spender, value), how filters combine, default behavior when no filters are provided, or the response shape. The description leaves significant gaps for the agent to infer.

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 coverage is 100%, so the baseline is 3. The description adds mild semantic value by stating 'for a token or address', which hints at using tokenAddress or ownerAddress/spenderAddress filters. However, it does not explain any relationships or constraints, such as whether at least one filter is required or how block range parameters interact.

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 ERC20 approval events and indicates two key dimensions (token or address). It uses a specific verb and resource, and distinguishes from related tools like get_token_approvals (current state) because it explicitly mentions 'events'. However, it does not explicitly clarify that these are historical event logs, which could cause ambiguity.

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 description provides no guidance on when to use this tool versus alternatives such as get_token_approvals, check_token_allowance, or get_erc20_transfers. It does not mention prerequisites like needing a token address or block range, and it does not explain any differentiation from sibling tools.

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