Set Illustrator Version

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

Annotations already declare it non-read-only, idempotent, and non-destructive, so safety is covered. The description adds real runtime behavior: it connects to an already-running instance regardless of the requested version, and otherwise launches the specified version — exactly the kind of side-effect detail annotations cannot express.

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?

Four short sentences, each carrying distinct information: purpose, format, running-instance branch, and reset flag. Nothing is padded and the core purpose leads.

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 no output schema and no required parameters, the description covers behavior, format, and the reset path adequately. It stops short of stating what happens if the requested version is not installed, a minor but real gap for a tool whose whole job is version selection.

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 goes further by giving an expected format example ('2024', '2025') and explaining the effective semantics of 'version' (ignored when an instance is already running) and of 'clear' (restores connect-to-any behavior).

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 ('set which Illustrator version to target') and immediately scopes it with the condition 'when multiple versions are installed.' No sibling tool overlaps with version targeting, so differentiation is easy.

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?

Clearly explains when the tool matters — multiple installs — and describes the connect-vs-launch branch plus the reset case. It does not enumerate alternatives, but there are no competing siblings for this capability.

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