afg2125_disconnect

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

The description clearly states the operation (close connection) and its scope (AFG-2125 VISA). No annotations conflict; the description adds context that this tool only affects the AFG-2125 connection. While it doesn't detail side effects, the operation is simple and straightforward.

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?

A single concise sentence that is front-loaded with the tool's purpose. Every word is meaningful, and there is no 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 zero-parameter disconnect operation, the description is complete. An output schema exists, so return values are already specified. The description fully covers what the tool does and its scope.

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?

The tool has zero parameters and the schema is empty. No parameter explanation is needed; the baseline of 4 applies since there are no parameters to document.

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 'Close only the AFG-2125 VISA connection' uses a specific verb ('close') and resource ('AFG-2125 VISA connection'). The word 'only' clearly distinguishes this from sibling disconnect tools for other devices or the generic 'disconnect_instrument'.

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 when to use this tool: when you need to close the AFG-2125 VISA connection specifically. It does not explicitly mention alternatives or exclusions, but the scope is clear from the 'only' phrasing and the sibling tool names.

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