mhs5200_connect

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds the behavioral detail that an existing connection is closed first, which is not obvious from annotations alone. This adds value beyond annotations.

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 concise (approximately 6 lines) and well-structured with separate sections for purpose, usage, args, and returns. Every sentence serves a purpose with no fluff.

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?

Given low complexity (1 parameter), rich annotations, and presence of output schema (provided in description as JSON format with fields status, model, serial), the description is complete and leaves no gaps.

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%, meaning the schema itself lacks parameter descriptions. The description fully compensates by documenting the 'port' parameter with examples and context (e.g., 'COM3', '/dev/ttyUSB0'), making it meaningful for the agent.

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 'Connect to MHS-5200A signal generator via serial port.' It uses a specific verb and resource, and distinguishes from siblings (e.g., configure, disconnect) by establishing this as the prerequisite connection step.

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?

Explicitly states 'This must be called before using any other mhs5200_* tools.' and 'If already connected, the existing connection is closed first.' This provides clear when-to-use and behavior on reconnection.

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