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

Annotations already cover readOnly/idempotent/non-destructive, and the description confirms 'Read-only, public' plus a key requirement (free key via a register URL) and the important note that clone_bot defaults to PAPER with simulated funds. These add real behavioral context beyond the annotations, though the auth/paper details pertain mostly to downstream tools rather than this one.

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?

Front-loaded with the purpose, then a compact arrow-chained workflow and the key requirement. It is dense but every clause carries useful routing or prerequisite information; the arrow notation is slightly run-on but still readable.

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 zero-parameter, no-output-schema tool, it covers what gets returned, the prerequisite key, and the follow-on calls. It is essentially self-sufficient for an agent deciding how to launch a clone workflow.

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 takes zero parameters, so the baseline is 4. The description usefully characterizes the return fields (source_type + source_id) that feed clone_bot, adding meaning beyond the empty schema.

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?

It states a specific verb and resource ('Lists every AI trading bot available to clone') and explicitly enumerates the categories returned (WTA species, perpetual agents, backtest bots). It also positions itself as the entry point ('start here'), making it distinguishable from the many other list_* siblings.

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?

It gives clear context as the first step and chains the downstream workflow (clone_bot -> fund_clone_bot -> toggle_bot_trading -> get_clone_balance). It does not, however, contrast itself against the other list_* siblings (list_funds, list_markets, list_clob_pairs), so alternative selection is only implied.

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