Lists available local printers with their names and drivers, helping AI agents discover print targets before sending print jobs.
列出本机可用的打印机（名称 + 驱动）
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "getPrinterList"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. '列出' signals a read-only, side-effect-free operation and it discloses the return payload (name + driver), but it says nothing about failure modes (no printers installed), whether driver info may be absent, or platform/OS scope beyond '本机'.
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 short sentence with zero waste, front-loading the action and parenthetically stating the return fields.
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?
A simple zero-argument list tool with no output schema; the parenthetical return-field note compensates for the missing output schema. Only the bridge to the print* tools, which consume these printer names, is left unstated.
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, so there is nothing to disambiguate; the baseline for a no-param tool is 4. The description correctly implies no filtering or arguments are 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?
States a specific verb and resource ('列出本机可用的打印机') and even names the returned fields (名称 + 驱动). It is clearly distinct from siblings like getPrinterPapers and the print* family, though it does not name a sibling explicitly to route the agent.
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?
Usage is only implied: an agent can infer this is a discovery step to run before the print* tools. There is no explicit statement of when to call it, prerequisites, or that printer names returned are the inputs for printHtml/printFile.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.