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

Annotations already indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds the behavioral detail that cloning can take a few minutes, which is useful. However, it does not elaborate on the exact scope of duplication (e.g., what is copied, whether original is affected), so it provides only moderate transparency beyond the annotations.

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 one sentence with two concise parts: the core action and a latency warning. It is front-loaded with the verb and resource, contains no filler, and every word contributes to understanding.

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 simple tool with a single well-documented parameter, an output schema, and annotations, the description is nearly sufficient. It covers the key purpose and the notable latency behavior, but it could mention what the clone operation returns or any post-conditions. Still, given the context signals, it is largely complete.

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 input schema fully documents the single parameter bot_id with a clear description. The HTTP endpoint in the description restates the same parameter, adding no new semantic meaning. Since schema coverage is 100%, the baseline of 3 applies.

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 clearly states the tool duplicates an existing agent, using the specific verb 'Duplicate' and resource 'agent'. It also provides the HTTP endpoint, which unambiguously identifies the operation and distinguishes it from sibling tools like create-agent or delete-agent.

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 on when to use the tool: to create a duplicate of an existing agent. It does not explicitly mention alternatives or exclusions, but the verb 'duplicate' inherently differentiates from create-agent, and the latency note provides additional usage context (not to be used for instant operations).

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