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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds real domain context the annotations cannot: runs can terminate when funds run out or the owner ends them, and real vs demo money with values sourced from BNB Chain versus a demo account. It does not mention result count, ordering, or whether ended runs are included.

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?

Three tight sentences, front-loaded with the resource and its URL, then the distinguishing real-versus-demo mechanic, then the returned fields. Slight density in the parenthetical 'value read from BNB Chain' clause, but nothing is wasted.

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 parameterless read-only list with no output schema, the description supplies what the returned entities are, the two modes that shape their values, and the per-run fields (start, current value, status). That is enough for an agent to call it and interpret results correctly.

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?

Zero parameters, so there is no parameter semantics to explain and the baseline applies. The 'paper: false / paper: true' explanation is genuinely useful, though it describes a field on returned runs rather than an input, which could momentarily be misread as a filter since no parameters exist.

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?

States a specific verb and resource ('Public runs on dolphinamp.xyz/live') and explains what a live run actually is: an agent trading in public until its money runs out or its owner ends it. It doesn't explicitly contrast with the singular sibling get_live_run, but the plural listing intent is unambiguous.

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?

Usage is implied by the word 'Public runs' and the sibling get_live_run, but there is no explicit 'use this when you want the list, use get_live_run for a single run' statement, and no note on ordering, limits, or when the list would be empty.

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