list_printers

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

With no annotations, the description carries the full burden, and it does disclose the shape of the return data (short names, with full machine preset names also acceptable). However it never says this is a read-only enumeration, whether results are scoped to installed/available printers, or how the list is ordered.

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 no waste, and the key fact (short names usable as printer identifiers) is front-loaded. It reads as a fragment rather than a complete statement of what the tool does, which slightly undercuts clarity.

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 tool with no output schema, describing the returned identifiers is the essential missing piece, and the description supplies it along with the interchangeability of preset names. Only the enumeration's scope and ordering are left unstated, which is a minor gap.

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 for the description to disambiguate; baseline 4 applies. The parenthetical about full preset names is a small extra hint for callers passing the results into other tools.

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 is a noun phrase that identifies the resource (printer short names) but never states the action; it relies on the tool name 'list_printers' to convey that a list is returned. It does distinguish the output from full machine preset names, which helps separate it from preset-related siblings, but the purpose itself is only implied.

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 hints at downstream usage ('can be used anywhere a printer is asked') but gives no guidance on when to call this versus siblings like list_user_presets, search_presets, or set_printer. No prerequisites, no exclusions, no alternative routing.

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