szlcsc_altium_setup

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

With no annotations, the description carries the full burden. It explicitly discloses a key behavior: this tool does not execute installation, only returns commands. This is valuable safety context. It doesn't mention other side effects, but the '返回命令' phrasing implies a read-only operation.

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?

Single sentence, front-loaded with the tool's purpose, and every word earns its place. No fluff or repetition.

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?

Given the tool has no parameters and an output schema exists, the description sufficiently covers purpose and the key non-execution behavior. It's complete for a simple diagnostic/command-return tool.

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 tool has zero parameters, so there is nothing to explain. Baseline of 4 applies since no parameter documentation is needed.

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?

Description tells us the tool returns diagnostics and safe install/upgrade commands, with a specific verb ('返回') and resource ('Altium 转换工具链'). It explicitly distinguishes itself from executing installation, which differentiates it from sibling tools like szlcsc_altium_import or szlcsc_altium_status.

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 statement '本工具本身不会执行安装' clearly tells the agent this tool is for retrieving commands, not performing installs. This implies when you need actual installation, you should look elsewhere, but explicit alternatives aren't named.

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