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

Annotations already flag readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is well covered. The description adds useful context about the data source (Covalent/GoldRush), multi-chain support, and included USD/gas fields, but it does not disclose pagination, rate limits, response shape, or chain-id edge cases.

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 two concise lines of prose followed by a concrete executable example, with no filler. The core scope is front-loaded and every sentence earns its place.

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 simple read-only tool with fully described parameters and clear annotations, the description plus schema is nearly sufficient. The absence of an output schema is partially mitigated by the mention of USD-valued amounts and gas, though a note about the response list shape or pagination would make it 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 provides 100% coverage of all three parameters with descriptions and examples, so the baseline of 3 applies. The description's example essentially duplicates the schema examples and adds no new meaning about formats, defaults, or constraints beyond what the schema already states.

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 defines the tool as fetching recent on-chain transactions for a given address on a chain, with USD-valued amounts and gas. This semantically distinguishes it from the sibling covalent_token_balances and covalent_token_holders tools, though it does not name an alternative and uses a noun phrase rather than an explicit verb.

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 the use case: when you need recent transactions for an address with USD-valued amounts and gas. It does not provide explicit when-not-to-use guidance or name alternative tools, so the agent must infer applicability from the word 'transactions' and the examples.

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