1s_events_live

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

No annotations provided, so description carries full burden. Discloses warning about large responses, describes output format (raw log entries with topics/data/block context), and mentions hex encoding. Does not cover error conditions 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?

Sentences are purposeful and front-loaded with purpose. Some redundancy in block range warnings, but overall concise for the detail provided.

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?

Covers all key aspects: what it does, filters, block range behavior, network selection, output shape, and performance warning. No output schema but description sufficiently describes return values. Minor gap: no mention of handling empty results.

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% but description adds value: explains topic0 as keccak256 hash with example, clarifies block params are hex-encoded. This goes beyond schema descriptions.

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?

Verb 'Query' plus resource 'raw event logs via eth_getLogs' clearly states purpose. No confusion with sibling tools like 1s_tx_receipt or 1s_block_by_number because it uniquely targets event logs.

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?

Explicitly advises keeping block ranges small, specifying contract address, and explains default behavior when from/to_block omitted. Lacks explicit when-not-to-use or comparison to siblings, but provides concrete usage constraints.

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