diagnostics

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

Discloses that it does not connect to fldigi, and details exactly what information it reports (resolved FLDIGI_HOST/PORT, Python version, hostname, transmit-gate state, network interfaces). No annotations provided, but description fully informs agent of behavior.

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?

Concise multi-sentence paragraph that front-loads the main purpose and adds necessary context efficiently. Every sentence adds value without 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?

Given zero parameters and no output schema, the description fully explains the tool's purpose, what it reports, and how to interpret results. It is complete for a diagnostic tool.

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?

No parameters exist, so baseline 4. The description adds no parameter info because none are needed.

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?

Clearly states it performs host and network diagnostics for troubleshooting connectivity. The description distinguishes itself from siblings by specifying its diagnostic scope, which is unique among the listed tools.

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 that it does NOT connect to fldigi, and provides guidance on what to do if a non-loopback host times out, directing to mcp-host-bridge docs. This helps the agent choose this tool for connectivity troubleshooting.

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