address_token_transfers

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

No annotations are provided, so the description must carry the burden. It does not disclose pagination, ordering, default behavior, or safety implications. The phrase 'from the explorer index' is too vague to inform the agent about performance or scope.

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 a single sentence, making it concise. However, it borders on under-specification. It could be expanded to include key details without becoming verbose.

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?

Given the lack of output schema and rich annotations, the description is too minimal. It does not clarify what the response contains (e.g., arrays of transfer objects, pagination info) nor how it differs from sibling tools. This leaves an agent underinformed for correct invocation.

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 0%. The description fails to explain the 'limit' and 'address' parameters beyond what the schema (names, types) already shows. For a parameter-heavy tool, this is insufficient.

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 'token transfers involving an address, from the explorer index.' It conveys the general domain (token transfers for an address) but lacks a specific verb like 'list' or 'get', and does not clarify whether it includes both sent and received transfers. It is somewhat clear but leaves room for ambiguity.

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 on when to use this tool versus alternatives like 'token_transfers' (likely global) or 'address_transactions' (includes non-token transactions). There is no explicit context or exclusion criteria.

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