set_setting

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

With no annotations, the description carries the full burden. It does disclose one genuinely useful behavioral trait — the override is session-scoped and therefore not persisted — but says nothing about invalid key handling, whether the key must already exist, or when the change takes effect relative to slicing.

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 front-loaded sentence with the action, scope, and two illustrative examples packed in without waste. Nothing could be removed without losing information.

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 two-parameter mutation tool with no annotations and no output schema, the description covers the essentials of what it does and how values look, but omits how to discover valid keys and what happens on failure. Adequate but with clear gaps for a state-changing 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?

Schema description coverage is 0%, so the schema gives no help on the two required parameters. The inline examples ('fill_density=20%', 'layer_height=0.15') do reveal the key naming convention and that values are passed as strings, which partially compensates, but there is no guidance on valid keys or accepted value formats.

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 ('Override a PrusaSlicer setting') plus a scope qualifier ('for this session'), which clearly separates it from get_setting and reset_setting. It never names a sibling explicitly, so it falls short of the 5 bar for sibling differentiation, but the purpose is unambiguous.

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 phrase 'for this session' implies the usage condition — temporary in-memory overrides rather than persistent profile edits (save_profile_as) — but this is left for the agent to infer. There is no explicit statement of when to prefer this over editing a config file or profile, and no exclusions.

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