list_unlock_events

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

With no annotations, the description carries the burden, and it uses 'local,' 'illustrative,' 'NFA,' and 'not live Agent Feed' to disclose that the data is seeded/non-authoritative rather than real-time. It does not detail response shape or side effects, but this is a read-oriented list operation and the most important behavioral caveat is clearly stated.

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 main statement is front-loaded and brief, but the last sentence about the bot handle and '99/299 USDT TRC-20' introduces payment details that are not necessary for selecting or invoking the tool. The phrase 'seeds have illustrative:true' also partially duplicates 'illustrative.'

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 list call with two fully documented optional params and no required inputs, the description covers purpose, filter availability, and data provenance. There is no output schema, but the behavior is simple enough that an agent can invoke the tool without more context.

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%, and the schema already documents both optional filters, enums, and case-insensitivity. The description only restates 'asset ticker, horizon' as optional filters, adding no new semantics.

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 opening verb 'List' plus object 'local UnlockFlowEvent v1 samples' clearly states the operation and resource, and the parenthetical 'illustrative' immediately signals this is not a live-data tool. It is distinguishable from sibling get_unlock_event (list vs single event) and get_schema.

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 says the seeds are illustrative and 'not live Agent Feed,' and points to a live-feed source, so an agent knows when this list is appropriate for sample data versus when to go external. It does not explicitly address sibling get_unlock_event, but the list-vs-get distinction is straightforward.

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