scope_setup_measurements

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

With no annotations, the description fully explains the tool's purpose and behavior: it sets up display slots, and only active parameters return valid values. It does not detail side effects like overwriting existing measurements, but the core behavior is transparent.

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?

Description is concise with a clear first sentence stating purpose, followed by a brief usage rationale, then parameter details in a structured list. No redundant sentences.

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?

Given the tool's complexity and the presence of an output schema, the description adequately covers setup purpose and parameter behavior. Mentions return value dependency on active slots, but could be enhanced by noting the output format or status. Still fairly complete.

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%, but the description fully compensates: explains channel is 1-4, params is a list of up to 6 string names, provides defaults, and lists all valid names. This far exceeds schema information.

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?

Clearly states the tool configures the measurement panel (P1-P6) for a channel, using specific verb 'Configure' and resource 'measurement panel'. Distinguishes from siblings like scope_measure and scope_measure_all by noting it's an explicit setup vs auto-configuration.

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?

Explicitly advises calling once after connecting to a new channel signal, and explains that scope_measure/scope_measure_all auto-configure but may be unreliable, making this tool the preferred explicit setup. Provides clear when-to-use guidance and alternatives.

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