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

No annotations are present, so the description carries the full burden. It discloses useful traits such as the on-chain nature, the specific data shape (USDC transfers to the fee receiver), and the x402 payment requirement. However, it does not explicitly state read-only behavior, output format, or failure/cost behavior beyond the mention of payment.

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, compact sentence that front-loads the core meaning and adds only two high-value clarifications: the transaction type and the payment mechanism. Every phrase 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?

Given that the tool takes no parameters and has no output schema, the description covers the essential context an agent needs: what the data is, where it comes from, and that it is paid via x402. It stops short of describing the returned record structure, but the low complexity makes this a minor gap.

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 tool has zero parameters, so there is nothing for the description to clarify beyond the schema. The absence of parameter documentation is not a gap because no inputs exist; the baseline of 4 applies.

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 names a specific operation (getting real on-chain sales history) and defines the data source precisely as USDC transfers to the Kristo fee receiver. This clearly differentiates it from the sibling tools get_bot_status and get_market_stats, which cover different domains.

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 about when to use this tool versus the siblings or when not to use it. The description does not mention alternatives, preconditions, or typical use cases beyond the implied one of fetching sales history.

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