列出连接 profile

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

No annotations are supplied, so the description must carry the behavioral burden. '列出' plus '已保存的' implies a read-only enumeration over persisted state, and the listed fields tell the agent roughly what comes back, but it does not state whether the read has side effects, whether it requires a live connection, or what happens when no profiles are saved.

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?

A single compact sentence that leads with the action and resource and ends with the consumable follow-up call. Nothing is padded and nothing essential is buried.

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 zero-parameter, read-only listing with no output schema, the description covers what is enumerated, the fields involved, and how the result is used downstream. Only the absence of annotations, and the resulting silence on permissions and empty-list behavior, keeps it from being fully self-sufficient.

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 takes zero parameters, which is the baseline-4 case. The description also clarifies that the port, baud rate, newline, and prompt values are properties of the returned profiles rather than inputs, which prevents schema confusion.

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 states a specific verb (列出/list) and a specific resource (已保存的串口连接 profile, saved serial connection profiles), and it names the fields such a profile holds (port, 波特率, 换行, prompt). This clearly separates it from live-port discovery such as list_ports, but it never names a sibling 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?

The closing phrase 'open({profile:name}) 一条复用' (one-line reuse via open with the profile name) gives concrete follow-on guidance for what to do with the listed names. However, there is no explicit when-to-use or when-not-to-use statement and no comparison with profile_save, profile_delete, or list_ports.

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