Write SCPI

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

No annotations are present, so the description carries the full burden. It usefully discloses the fire-and-forget semantics ('no reply'), which is the main behavioral trait, but says nothing about error handling, whether execution blocks, or that commands like *RST are destructive/irreversible outside the schema's confirm note.

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 sentence, leading with the verb and the decisive 'no reply' constraint before the examples. Zero wasted words and nothing buried.

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 need no explanation, and the core no-reply semantic is covered. However, for a 3-parameter tool with zero annotations, it omits prerequisite/error context and any mention of the `resource` parameter's role, leaving gaps an agent must fill by opening the schema.

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 is 67%, so the schema already documents `command` and `confirm` in detail. The description's examples (settings, *RST, :RUN) illustrate what `command` accepts and implicitly connect *RST to the confirm requirement, but it adds no syntax or format guidance and says nothing about the `resource` parameter.

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 states a specific verb (Send) and resource (SCPI command) and pins the key scope constraint with 'with no reply,' which is what separates it from the sibling `query`. Concrete examples (settings, *RST, :RUN) make the intent unmistakable, though it never names the sibling it complements.

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?

'with no reply' implies the when-to-use condition and the examples show the class of commands, but the alternative (`query` / `query_binary`) is never named and there is no explicit 'use query when you expect a response' rule. Usage is inferable rather than stated.

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