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

With no annotations provided, the description carries the burden of behavioral disclosure. It states that the tool loads an iteration onto the live canvas and that subsequent mutate tools act on it, but it does not mention side effects like replacing the currently selected iteration, persistence, or error conditions. This is adequate but has clear gaps.

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?

One sentence, front-loaded with the core action, and the purpose clause earns its place. There is no wasted wording or redundant repetition of schema content.

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 2-parameter tool with no output schema and no annotations, this is minimally sufficient: the agent knows what to load and why. However, it lacks guidance on when strategy_id matters, what happens to the previous canvas selection, and what a successful load returns or signals.

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%, so the schema already explains both 'ref' and 'strategy_id'. The description adds little parameter-level meaning beyond naming the @R# as the thing loaded; it does not elaborate on the optional strategy_id or when to use it.

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 uses a specific verb ('Load') and a specific resource ('@R# onto the live canvas'), then explains the purpose ('so mutate tools edit that iteration'). This clearly distinguishes it from the read/list/get siblings and the patch/delete mutation tools.

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 phrase 'so mutate tools edit that iteration' provides clear contextual guidance: this tool should be called before applying mutations such as patch_cooldown, patch_entry_gate, or patch_exit. It does not explicitly say when not to use it or name alternatives, 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.