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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile needs no repetition. The description adds genuine context beyond the annotations by enumerating the returned fields (time, sender, receiver, amount, tx hash), which matters because no output schema exists, but it does not disclose ordering, pagination behavior beyond the schema's limit note, or behavior on non-ERC-20 tokens.

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 front-loaded sentences plus a worked example: the core purpose and return shape come first, and the example is a compact illustration. The example is somewhat redundant with the schema's own examples, which is a minor waste, but overall every part serves comprehension.

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 read-only list tool with strong annotations, full schema coverage, and the return fields stated in the description, an agent has what it needs to invoke the tool correctly. Minor gaps remain — result ordering is only implied by the word 'Recent', and token-format expectations rest on the schema example — but these are not material.

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 description coverage is 100%, so the schema documents all four parameters and the baseline of 3 applies. The description's example call usefully grounds a real invocation with a concrete token address and network value, but it is largely redundant with the examples already present in the input schema.

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 clear verb-and-resource pair: it returns ERC-20 transfer events for a token contract on an EVM chain via Bitquery, with return fields enumerated (transfer time, sender, receiver, amount, tx hash). It is unambiguous about what the tool does, though it never names or differentiates itself from the sibling tools bitquery_dex_trades and bitquery_token_holders within the description text.

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?

No guidance is given on when to choose this tool over its siblings; the description does not mention alternatives, exclusions, or preconditions such as needing an ERC-20 contract address. The only cross-reference is in the schema's network parameter pointing to bitquery_dex_trades for enum options, which concerns parameter values rather than usage selection.

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