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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the bar is lower. The description adds real context beyond them: that this endpoint itself is public and keyless ('Read-only, public'), while the follow-on tools need a free key, and that omitting paper=false silently produces a PAPER (simulated) clone — a behavioral trap worth disclosing. It does not state ordering, pagination, or whether results can be empty.

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?

Purpose is front-loaded in the first two sentences, then the workflow chain, then the access requirement — a sensible order with no filler sentences. It is somewhat overstuffed for a zero-argument lister, carrying onboarding-chain and registration-URL detail that arguably belongs to clone_bot.

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?

With no output schema, the description steps in to say the response carries source_type + source_id and which bot species appear. Combined with annotations covering safety and a zero-param schema, that is nearly enough to call it correctly, though the full shape of each listed bot (name, performance figures, ids) is left unstated.

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 there is no parameter semantics to compensate for and the baseline of 4 applies. The description correctly implies a no-argument call by describing a full listing rather than any filtering options.

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: 'Lists every AI trading bot available to clone' and enumerates the species included (WTA species, perpetual agents, backtest bots). It also names the fields the listing yields (source_type + source_id) and the sibling it feeds (clone_bot), so an agent can distinguish it from get_my_clones without opening either 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?

Provides unusually explicit entry-point guidance ('start here') plus the exact downstream sequence: get_deposit_address -> clone_bot(paper=false) -> fund_clone_bot -> toggle_bot_trading -> get_clone_balance. It also flags the key requirement and points to a registration endpoint. It stops short of stating when NOT to use it or contrasting it with sibling listers like get_my_clones or list_backtest_surfaces.

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