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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses atomic patch behavior with hard errors on unresolved paths, dry-run no-persist semantics, zero research token cost, and fresh strategy IDs in the copied portfolio, all of which go well beyond a generic 'creates a copy' statement.

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?

Every sentence earns its place: core action, clone-versus-edit mode, error semantics, dry-run behavior, and cost. The description is compact, front-loaded with the main purpose, and contains no fluff or redundant restatement of schema properties.

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 tool with no annotations and no output schema, the description plus the rich input schema gives an agent everything needed to select and invoke it correctly: source identification, patch constraints, action-type-specific sizing, atomicity, dry-run behavior, and cost. The lack of explicit return-shape details is not a blocker 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?

The input schema already provides 100% description coverage, so the baseline is 3; the tool description raises it by clarifying cross-parameter behavior: omitting patches yields a clone, providing patches yields surgical edits, and dry_run changes whether anything persists. It also adds the atomic hard-error behavior for unresolved patch paths, which is absent from the schema text.

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 first sentence names a specific action ('deep-copy'), a source ('source chat or deployed portfolio'), and a target ('new ChatPortfolio with fresh strategy IDs'), making the tool's create-and-copy purpose unmistakable. This clearly distinguishes it from siblings like update_portfolio, which mutates an existing portfolio, and build_portfolio, which would create from scratch.

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 usage modes: omit patches for a clone-only draft, apply JSON-Pointer patches for surgical edits, and use dry_run to validate without persisting. It does not explicitly name sibling alternatives or exclusion conditions, but the source-copy semantics and mode guidance are enough for an agent to decide when this tool fits.

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