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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint and openWorldHint, so the bar is lower, yet the description still adds real behavior: a 100-log result cap, block-range limits, and that each call is billed ($0.01, first 25 free, failed calls free) so repeats are not free. That billing/idempotency context is exactly the kind of trait an agent cannot infer from structured fields.

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?

Front-loaded with the core verb and resource, and every clause carries information (range, filter, return shape, alternative, price). The second half is dense with semicolon-joined clauses on billing and safety, which is efficient but slightly harder to scan.

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?

No output schema exists, so the description supplies the return shape itself ('up to 100 logs with block, transaction hash and topics'), plus scan limits, filtering, alternative routing and pricing. Nothing material is missing for calling this tool correctly.

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 all three parameters are already documented, including the 1-1000/default-50 range on blocks. The description restates the block range and expands topic0 only slightly ('0x 32-byte event signature hash'), which largely mirrors the schema text; the example address is a sample value rather than added semantics.

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?

States a specific verb and resource ('Recent contract event logs on Sei (eth_getLogs)') plus the scope of what is returned. It distinguishes itself from the nearest sibling by naming sei_receipt as the tool for single-transaction outcomes.

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?

'Use to watch transfers or contract events; for one transaction's outcome use sei_receipt' gives a clear condition and explicitly routes one case to an alternative. It does not clarify the boundary against sei_token_transfers, which is arguably the most tempting sibling for the 'watch transfers' use case it recommends.

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