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

With no annotations provided, the description carries the full behavioral burden and does a good job: it discloses the paid nature of the call, the upstream URL, the HTTP method, and the available filters. It does not mention rate limits or response shape, but the core read-query behavior and cost are clear.

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 dense and efficient; billing, purpose, upstream endpoint, method, and an example are all packed in without fluff. It is somewhat run-on and lacks clear sentence breaks, but every segment earns its place and the most important details are front-loaded.

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?

For a tool with no output schema and no annotations, the description provides enough to make a basic call using the example, but it leaves the exact syntax for topic and block-range filtering undocumented. The upstream URL helps, but an agent would still need to infer parameters for anything beyond the simplest contract-address query.

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 only exposes generic body and query objects, but the description adds real parameter meaning through an explicit example query with contract and network fields. It also names conceptual filters (contract, topic, block range), going beyond the generic schema while not fully documenting every parameter name or type.

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 verb and resource: "Query Ethereum contract event logs via eth_getLogs." It also names concrete filters (contract, topic, block range), which clearly distinguishes this from the many sibling chain tools for balances, transfers, and transactions.

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 gives clear context for when to use this tool: whenever Ethereum contract event logs are needed. It does not explicitly name sibling alternatives or state when not to use it, but the purpose is specific enough that selection is not ambiguous.

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