configure_measure_region

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

With no annotations, the description carries the full burden. It adds some behavioral context (ZOOM requires delayed sweep, link_cursors ties cursors, references SCPI command) but omits side effects, persistence, and interaction with other measurement settings.

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 front-loaded with the tool's purpose, then uses a compact list for parameters. Every line earns its place with no filler.

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 are not needed. However, for a configuration tool with no annotations, the description lacks broader usage context and behavioral details beyond parameter semantics, leaving gaps.

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 0%, so the description must compensate. It does so thoroughly by defining allowed values and semantics for area, type, cursor_ax, cursor_bx, and link_cursors, including units and the condition 'for area=CURSor'.

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 clearly states the tool configures the measurement range (gating region), a specific resource. It does not explicitly differentiate from siblings like configure_measure_setup or set_cursor, 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 description lists parameter options and their meanings, but provides no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites beyond the note that ZOOM 'needs delayed sweep'.

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