scope_set_panel_lock

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

No annotations are provided, so the description must carry full burden. It specifies the action (lock/unlock) and mentions 'Transport: SCPI' but does not disclose side effects, persistence, or impact on other operations. Minimal behavioral detail beyond the obvious.

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 very concise: one line for purpose, one line for parameter explanation, and one line for transport protocol. No unnecessary words, and the purpose is front-loaded.

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?

Tool is simple with one parameter and an output schema exists but is not provided in the description. The description does not mention what the tool returns (e.g., success/failure, current state). Without output schema or return details, the agent lacks complete context for execution.

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?

Input schema has one boolean parameter with only a title. Description adds meaning: 'True to lock (prevent accidental adjustment), False to unlock.' This clarifies the purpose of the boolean value, compensating for schema's lack of description.

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?

Description clearly states 'Lock or unlock the oscilloscope front-panel controls' with a specific verb and resource. It distinguishes from sibling tools, none of which focus on panel lock/unlock.

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?

Description provides context for locking ('prevent accidental adjustment') but does not explicitly state when to use this tool vs alternatives or when not to use it. No exclusions or alternative recommendations are given.

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