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

Annotations already declare readOnlyHint=false (mutation), destructiveHint=false, and openWorldHint=false. The description adds no behavioral context beyond restating 'Duplicate' — it does not say what the duplicate inherits, whether the original is affected, or what the response contains. It is consistent with annotations but mostly redundant.

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 short sentences with the purpose front-loaded and no wasted words. The endpoint path is included but adds little practical value for an agent that already has the tool name; still, it is efficient and structured.

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 mutation tool with a nested required body, no output schema, and no annotations covering return behavior, the description is too sparse. It omits what the duplication returns, whether the new bot has a distinct name, and any auth or rate-limit context, leaving significant gaps 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?

Schema description coverage is 0% for the top-level body parameter, and the description adds no parameter meaning at all. The nested id field has a schema description ('Bot ID to duplicate'), but the tool description does nothing to compensate for the coverage gap or clarify what identifier format is expected.

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 clear verb ('Duplicate') and a specific resource ('prediction signal bot'), which distinguishes it from generic bot operations. However, it does not differentiate from sibling duplication tools like post_bot_signal_cex_duplicate, leaving the agent to infer scope from the resource name alone.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states the operation, leaving the agent to guess usage context entirely.

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