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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds the authentication requirement and how to obtain the key (register_agent, no key needed) plus the REST twin endpoint, which is genuine behavioral context beyond the structured fields. It stops short of noting pagination or result limits.

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?

Four tight sentences with zero filler, and the blocking prerequisite (api_key) is front-loaded before the payload description. The parenthetical field list is dense but 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 read-only list tool with full annotation coverage and a 100%-documented schema, the description supplies the missing pieces an agent needs: auth requirement, ownership scope, returned fields, and the REST twin. Only minor gaps remain (no mention of include_inactive or pagination behavior).

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?

Schema description coverage is 100%, so the schema already documents mode, api_key and include_inactive; the baseline is 3. The description reinforces mode's paper|live semantics but adds no syntax or format detail beyond the schema, and it never mentions include_inactive at all.

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 with clear ownership scope ('bots YOU have cloned'), which implicitly separates it from the sibling list_clonable_bots (bots available to clone). It also enumerates the returned fields, so an agent knows exactly what it gets.

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 a real prerequisite ('Needs your api_key', with a pointer to register_agent) and a filter hint ('mode=paper|live'), which is more than bare implied usage. However, it never states when to prefer this over siblings like list_clonable_bots or get_clone_balance, and offers no exclusions or conditions for choosing it.

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