vna_software_hide

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

With no annotations, the description carries full responsibility for behavioral disclosure, but it only states the bare action. It does not mention side effects, whether a connection is required, persistence of the hidden state, or how to reverse it.

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 maximally concise and front-loaded with the verb 'Hide', containing no wasted words. However, it is under-specified, but conciseness itself is acceptable because every word contributes to the minimal meaning.

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 tool has parameters, no output schema, and no annotations; the description provides no contextual information about prerequisites, expected behavior, return values, or how it fits into the larger VNA workflow. It is incomplete for an agent to use correctly.

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%, and the description does not explain the host and port parameters at all. The agent receives no guidance on what these parameters mean, whether they are required, or what values are expected.

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 the action (hide) and the resource (VNA software UI), distinguishing it from the sibling tool vna_software_show and other VNA tools. It is specific and unambiguous, even though it is brief.

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 gives no guidance on when to use this tool versus alternatives, no prerequisites, no exclusions, and no mention of the show counterpart. An agent has no context for when this should be invoked.

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