reset

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

With no annotations, the description carries the full burden. 'Restore default instrument settings' does disclose the core mutating effect (existing settings are replaced), which is the key behavioral fact. It omits the practical consequences, however: no warning that current/unsaved setup is lost, no note about post-reset settling time, and no mention of whether a subsequent self_test or wait_complete is needed.

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 that names the SCPI command and its effect with no filler. Every word earns its place.

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 an output schema (so return values need not be described) and an empty schema, the description covers the essential action. The only gap is the lack of any caution about what state is discarded, which would be minor for a simple reset.

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 and the schema is empty, so there is nothing to document; baseline 4 applies. The description correctly implies no arguments are required.

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 (send *RST) and the resulting resource effect (restore default instrument settings). This is more informative than a bare 'reset' and implicitly distinguishes it from reboot_system (power cycle) and clear_status (status registers). It stops short of explicitly naming those siblings, so a 5 isn't warranted.

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?

No when-to-use guidance: nothing says whether this should be used before a measurement session, how it differs from reboot_system, or whether it should be paired with load_setup to restore a saved configuration. The agent must infer context entirely.

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