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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond annotations by stating the operation is public and scoping the result set to clonable bots and their source fields. No contradiction exists.

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 two sentences with no filler. The primary action and resource are front-loaded, then scope categories and purpose are given, followed by the read-only/public qualifier. Every clause 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?

For a zero-parameter, read-only, public list tool with no output schema, the description is complete: it states what is listed, which categories are included, what fields are returned, and why the agent would call it. Nothing critical is missing for correct invocation.

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 the description carries no parameter-documentation burden. The baseline of 4 applies, and the description still adds value by explaining that the returned source_type/source_id pair is what clone_bot consumes.

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 states a specific verb ('List'), a precise resource ('every AI trading bot available to clone'), and enumerates the relevant categories (WTA species, perpetual agents, backtest bots). It also names the output fields and their purpose ('source_type + source_id for clone_bot'), making the tool clearly distinguishable from nearby siblings like list_backtest_surfaces or get_backtest_models.

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 gives clear context: this tool is the source for clone_bot identifiers, and notes it is public. It does not explicitly state when to prefer an alternative, but the 'for clone_bot' purpose provides a strong implied usage rule for an agent deciding between tools.

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