spoolman_get_setting

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. While 'Retrieve' implies a read-only operation, the description does not state what happens if the key does not exist, whether the response includes metadata, or any potential error behavior. This is a minimal transparency statement.

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 a single sentence that is direct and front-loaded. Every word contributes to the tool's purpose, with 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?

For a one-parameter getter, the description is functionally sufficient but lacks detail about the return format (e.g., whether it returns a plain value or an object) and error handling. Since there is no output schema and no annotations, these omissions are notable, though the simplicity of the operation keeps it from being incomplete.

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?

Schema coverage for the single parameter 'key' is 100%, and the description simply restates 'by key' without adding new semantics. The baseline of 3 is appropriate because the schema already describes the parameter fully; no additional context 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?

The description uses a specific verb ('Retrieve') and clear resource ('Spoolman configuration setting') with a method ('by key'), making the tool's function immediately obvious. It also distinguishes itself from siblings like spoolman_get_all_settings by noting 'single'.

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 description gives no guidance about when to choose this tool over alternatives such as spoolman_get_all_settings or spoolman_set_setting. It does not mention contexts where a single setting is needed, nor does it exclude use cases.

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