identify_tcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not explicitly state that this is a read-only operation, what happens if no session is connected, or any error/timeout behavior. The only behavioral trait mentioned is that it operates on a 'connected raw TCP session', leaving other aspects undisclosed.

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 wasted words. It states the core action and resource directly. However, it may be considered under-specified for a full tool description, but that is more relevant to other dimensions.

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 description covers the basic action and resource but omits important contextual details such as the prerequisite of an active TCP connection and how this tool fits into the workflow relative to siblings like connect_tcp and disconnect_tcp. The presence of an output schema likely explains return values, but usage context is incomplete.

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 coverage is 100% (vacuously). The description adds no parameter semantics, but none are needed. The baseline of 4 applies because 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 uses a specific verb ('Query') and clearly identifies the exact resource (the SCPI command '*IDN?') and the communication channel ('connected raw TCP session'). This clearly distinguishes the tool from siblings like 'configure_channel_tcp' or 'measure_tcp', which perform different actions.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that an active TCP connection is required (e.g., via connect_tcp), nor does it contrast with other query or identification tools. The only implied guidance is the phrase 'connected raw TCP session', which suggests a prerequisite but does not explicitly state it.

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