set_autoset_options

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

With no annotations the description carries the full burden. It usefully discloses that enable=False disables :AUToset, mirroring lock_timebase=True, and that no autoset is executed. However, it omits the behavior of the other five flags, partial-update semantics, and any side-effect detail beyond enable.

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 key distinction is front-loaded in the first line, and the enable note is scoped separately. Some content (SCPI command name, section reference '3.2.7') is arguably noise, and the format is informal, but it stays short.

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?

An output schema exists, so return values needn't be described. But with no annotations and six schema-undocumented parameters, the description is too thin to call this tool correctly, covering only one parameter and relying on an external sibling for the rest.

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% across 6 parameters, so the description must compensate. It only explains 'enable' (master on/off, SCPI :AUToset:ENAble) and offloads the rest to 'Same parameters as autoscale()', leaving five flags undocumented anywhere.

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+resource ('Configure the AUTO (autoset) options') and adds a scoping clause ('WITHOUT executing an autoset') that distinguishes it from the sibling autoscale. An agent can tell this configures rather than triggers without opening the schema.

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 'WITHOUT executing an autoset' clause implicitly routes the agent to autoscale() when an actual autoset is wanted, and 'Same parameters as autoscale()' links the two. There is clear context but no explicit when/when-not statement or direct naming of the alternative.

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