Save Altium X2.EXE path

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

The description goes beyond annotations by revealing the persistence side-effect: 'Writes %USERPROFILE%\.altium-mcp\config.json (or equivalent).' It also explains error behavior when the file is missing and that the env var overrides at runtime without persisting. No contradiction with idempotent=true or destructive=false.

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 well-structured with labeled sections (Purpose, When to use, Parameters, Returns, Prerequisites, Notes). It is concise enough while covering all relevant aspects, front-loading the primary purpose and usage trigger. No wasted words.

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 one-parameter configuration tool, the description covers purpose, trigger condition, parameter semantics, return value, error case, prerequisites, and important runtime override behavior. With good annotations and full schema coverage, this is complete and leaves no gaps.

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% coverage with a clear description and example for 'path'. The description adds little beyond restating 'file must exist' and 'absolute path', which are already in the schema. Baseline 3 is appropriate since schema carries the full semantic load.

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: 'Persist the absolute path to Altium X2.EXE for bridge launches.' It clearly distinguishes this tool from sibling get/edit tools by focusing on persistent configuration of the executable path.

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?

It explicitly states when to use the tool: 'get_server_status shows altiumExeFound false or wrong AD version path.' It also notes an alternative (env var override) and clarifies that this method is persistent while the env var is not, giving clear decision guidance.

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