dex_list_events

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

Without annotations, the description carries the burden. It discloses that the tool lists indexed events with a restart-safe cursor, indicating it is a read operation with pagination. However, it does not explicitly state it is read-only or explain behavior for invalid parameters.

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, front-loaded with the action. It is efficient but lacks structure like bullet points for parameters. The conciseness is good, but the structure could be improved for clarity.

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 no output schema, no annotations, and no parameter descriptions, the description is somewhat minimal. It hints at cursor pagination and event types but does not cover output format or parameter details. It is adequate for a specialized tool but not fully complete.

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 input schema has 4 parameters with zero schema description coverage. The description does not explain any parameter (e.g., what 'event' lists, how 'after_id' works, or what 'contract' filters). This is a significant gap.

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 it lists indexed canonical DEX or bound LP-token events with a restart-safe cursor. This is specific and distinguishes it from siblings like 'list_events' (generic events) and 'dex_wait_live_event' (live events).

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 implies usage for DEX-specific event listing with cursor pagination but does not explicitly state when to use it over alternatives (e.g., 'list_events' for non-DEX events). No when-not-to-use or prerequisites are mentioned.

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