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

Far beyond the annotations: it enumerates exactly what is never copied (credentials, broker bindings, grants, deployments, orders, prompts, runtime notes, trading state) and discloses publisher-permission, purchase, and published-revision-only constraints. A minor gap is that it does not state what the call returns (e.g. new strategy id) or whether cloning is rate-limited, but the disclosure of copy scope and preconditions is unusually rich.

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?

Front-loaded with the core action, then ordered by scenario (Marketplace copy, owned copy, share-link copy, exclusions). Dense but every sentence carries a distinct constraint; the mid-paragraph diversion into 'normal deployment review' workflow is the only part that slightly dilutes focus.

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 six optional parameters, no output schema, and minimal annotations, the description supplies exactly the missing context: which id drives which copy mode, what preconditions must hold, and what the copy deliberately excludes. An agent can select and invoke it correctly without further reading.

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 coverage is 100%, so baseline is 3; the description adds real semantics beyond the schema by explaining the listingId/strategyId precedence and that listingId always yields only the explicitly published revision, even for the publisher. It does not cover shareToken/sharePassword/aiStrategyId in the prose, leaving those to the schema.

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 opening sentence gives a concrete verb, resource and key qualifiers: 'Creates a private dormant copy for the authenticated user.' It then distinguishes the two sourcing modes (strategyId for owned private history vs listingId for Marketplace published revision), which separates it from siblings like create_strategy or private_share_link.

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 explicitly names the condition for each parameter path ('To copy a Marketplace listing, pass its listingId from marketplace_strategies' vs 'Pass strategyId to duplicate owned private history') and names the sibling tool to get the id from. It also states when NOT to continue into code editing or backtests unless separately requested, and flags the paid-listing precondition.

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