scope_device

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

Annotations only provide readOnlyHint=false and destructiveHint=false. The description adds a generic return format and mentions session connection and health status, but it does not disclose consequences such as what 'connect' does to an existing session, whether 'disconnect' closes resources, or what data 'capabilities' returns. No contradiction with annotations, but behavioral depth is limited.

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, followed by a compact return format and four representative examples. Each section contributes useful information, and there is no filler or redundancy.

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 multi-operation device-management tool with no output schema, the return contract and examples are helpful. Minor gaps remain: the 'capabilities' operation is not exemplified, and the relationship to sibling tools is not spelled out, but the enum and parameter descriptions cover most mechanical detail.

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 description coverage is 100%, so the schema already documents operation, device_id, and backend. The examples illustrate valid combinations such as device_id='sim-001' but do not add substantive meaning beyond what the schema already provides.

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 opens with specific verbs and a clear resource: 'Discover, connect, and manage USB oscilloscope devices.' It then enumerates the consolidated responsibilities — device enumeration, session connection, backend selection, and health status — which effectively distinguishes it from the capture, configure, measure, and trigger siblings.

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?

Usage context is implied through the operation list and examples, but the description never explicitly tells an agent when to use scope_device versus scope_capture, scope_configure, or scope_measure. There are no exclusions or direct references to alternative tools.

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