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

With no annotations provided, the description carries full responsibility and handles it well. It discloses that only public on-chain data is returned, that no enrichment or identity inference occurs, that any address can be queried without authorization, and that the operation is a read. This goes well beyond a generic 'get history' statement.

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 efficiently structured, with the core question and constraint front-loaded, then content details, then a practical use case. A small amount of redundancy exists between 'no enrichment' and the later enumeration of absent clustering/labelling, but each sentence still contributes useful context.

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 two-parameter read-only tool with no output schema, the description covers what the response contains, the data source, the authorization model, and the intended user scenario. It does not describe response shape, ordering, pagination, or time-range behavior, which would add completeness, but the described scope is sufficient for correct selection and 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 100%, so the schema already fully documents both address and network, including defaults and testnet caveats. The description does not add new parameter-level detail, which is acceptable under the baseline but earns no extra credit.

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 opens with a direct question that defines the tool's job, then enumerates concrete answer content: auctions originated, bids placed, positions opened/closed, and outcome summaries. It also draws meaningful contrast with the sibling set by emphasizing raw public chain events with no enrichment, clustering, or inferred identity, which distinguishes it from tools like get_user_positions or check_wallet_status.

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 this tool is appropriate: it is the supervisor page's data source for checking what an agent has actually done, and it states that no authorization is needed for any address. It does not explicitly name alternatives or state when not to use it, but the use case and scope are specific enough to guide selection.

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