connect

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

The description adds 'Returns device identification on success' and specifies TCP, but it does not disclose that the connection is persistent or that it should be terminated with 'disconnect'. Annotations provide openWorldHint=true but do not cover connection lifecycle. The description is adequate but not rich in behavioral detail.

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?

Two concise sentences that front-load the primary action and mention the success return value. No redundant or vague wording; every sentence contributes valuable information.

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 simple connection tool, the description covers the essential aspects: connection address, protocol, and return value. It is slightly incomplete by not stating that the connection persists or that 'disconnect' should be used, but the sibling tool list makes this inferable. Overall, it is well-rounded for the tool's complexity.

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 coverage is 100%, with host and port both having descriptions including defaults and environment variable fallback. The description adds no new parameter-specific semantics beyond mentioning TCP, which is already implied by the port default of 5025. Baseline 3 is appropriate.

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 the tool's function: 'Connect to a Siglent SDG waveform generator over TCP.' It uses a specific verb (Connect), identifies the resource (Siglent SDG waveform generator), and specifies the protocol (TCP), making it distinct from siblings like 'disconnect' and 'identify'.

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 that this tool should be used before other operations (as it establishes a connection), but it does not explicitly say 'use before sending commands' or mention alternatives. There is no exclusion guidance, but the purpose is self-evident given the sibling tools.

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