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

With no annotations, the description carries the behavioral burden, and it does disclose the destructive default ('Replace... entire strategy set'), source/target validity, and the no-implicit-backtest rule. It does not explicitly state in the main description that prior target strategies are archived and their open system orders cancelled by default—that detail lives only in the preserve_existing parameter schema—and the phrase 'deep copies... by reference, not YAML' is slightly ambiguous.

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 front-loaded with the core operation, followed by the main use case and guardrails; almost every sentence earns its place. It is slightly long and partially restates schema constraints such as 'the target MUST be a real deployed portfolio', which prevents a 5.

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 no annotations and no output schema, the description is unusually complete: it covers source types, target immutability, copy semantics, replacement behavior, and the post-clone backtest policy. Combined with the detailed input schema and sibling fetch_portfolios for ID discovery, an agent has enough context to invoke it correctly.

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% and the parameter descriptions are already detailed, including preserve_existing behavior, source portfolio types, and the deployed-target restriction. The description reinforces the target constraint and workflow context but adds no genuinely new parameter-level semantics, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Replace a deployed (paper/live) portfolio's entire strategy set with deep copies of a source portfolio's strategy objects.' It also states the concrete use case—deploying a chat portfolio's strategies onto a live/paper portfolio without re-describing them—which clearly separates this tool from broader portfolio-building siblings.

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 an explicit trigger: 'Use this to deploy a chat portfolio's strategies onto a live/paper portfolio without re-describing them.' It also adds important boundaries: 'Do NOT automatically backtest after clone' and 'chat portfolios are immutable and cannot be a target.' It does not explicitly name sibling alternatives such as fork_shared_portfolio or update_portfolio, so it stops short of a 5.

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