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

Annotations cover read-only safety, open-world, non-idempotent and non-destructive traits, and the description adds pricing/auth context ($0.01/call via x402 USDC or card key, first 25 free, failed calls free) plus non-idempotence warning ('each call is charged, so repeats are not free'). It also discloses result caps (up to 100 logs). It does not explain pagination beyond the cap, which is a minor gap.

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?

Purpose and scope are front-loaded, then filters, then return shape, then routing to a sibling, then pricing. It is dense but every clause earns its place; pricing details add slight bulk but are behaviorally relevant.

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 3-parameter read-only log query with no output schema, the description covers scope, filter semantics, return shape (block, transaction hash, topics), limits, cost model, and the sibling alternative. Nothing material to correct invocation is missing.

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 schema already documents all three parameters including ranges and defaults. The description adds interpretation of topic0 as the 0x 32-byte event signature hash and an example address, but largely restates schema content, so baseline 3 applies.

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+resource ('Recent contract event logs on Linea (eth_getLogs)') and clarifies the scope as events a contract emitted over the last N blocks. It also explicitly distinguishes itself from the sibling linea_receipt ('for one transaction's outcome use linea_receipt').

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?

Gives explicit when-to-use guidance ('Use to watch transfers or contract events') and names the alternative with the condition that selects it ('for one transaction's outcome use linea_receipt'). It also includes a concrete example call.

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