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

With no annotations, the description carries the full burden and does meaningful work: it discloses that mirrored paper positions are closed and that reserved allocation returns to the wallet. It omits irreversibility, what happens if no copy is active, and any auth expectations, which keeps it below 5.

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 purpose and effects are front-loaded in one sentence with no filler. The trailing 'Args:' block is a mild structural redundancy rather than waste, and the docstring formatting is unnecessary given a formal input schema.

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?

An output schema exists, so return values need not be explained, and there is only one required parameter. The remaining gap is the precondition for calling it and post-call state — an agent could not tell from this whether calling it without an active copy is a no-op or an error.

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 0%, so the single parameter is undocumented structurally; the description supplies the key semantic clarification that fund_id is the fund being copied (not a copy record id). It does not give the type (integer) or how to discover valid ids (list_my_copies / list_funds).

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?

States a specific verb and resource ('Stop copying a fund') and immediately enumerates the two concrete effects. It is clearly distinguishable from start_fund_copy and adjust_fund_copy by the verb, though it never names those siblings explicitly.

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?

Usage is only implied — the agent must infer that this applies to an active copy. There is no explicit statement of when to call this versus adjust_fund_copy, and no stated precondition (e.g. an existing copy must exist).

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