self_test_device

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

Even though annotations already indicate readOnly=true and destructiveHint=false, the description adds valuable behavioral context: the test is 'brief' and it intentionally does not establish electrical safety. This goes beyond what the annotations provide and helps the agent set proper expectations.

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 a single, front-loaded sentence with no superfluous words. It conveys both the action and a critical caveat, making every word earn its place.

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?

The tool is simple with one required parameter and an output schema. The description covers the core action and a safety caveat, which is adequate for basic selection. It does not detail prerequisites or result interpretation, but given the output schema's existence, this is acceptable.

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 0%, and the description does not explain the 'device' parameter's format, allowed values, or meaning beyond the tool's name. The only compensation is that the word 'device' appears in the description, but this is insufficient for a low-coverage situation.

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 action ('Run') and the resource ('NI-DAQmx's brief device self-test'), making the purpose explicit. It does not explicitly differentiate from sibling tools, but the self-test action is distinct enough that the score is 4 rather than 5.

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 implies usage for running a quick device self-test and includes a caveat that it does not establish electrical safety, which hints at a limitation. However, it lacks explicit guidance on when to use this tool versus alternatives like get_device_details, so it does not fully meet the 'clear context, no exclusions' criteria.

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