vna_save_screenshot

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only restates the tool's name. It omits details about file overwriting behavior, required permissions, or whether a connection is needed, leaving the agent uninformed about side effects.

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, efficient clause with no redundant words. It is appropriately sized for a straightforward screenshot operation, though the brevity sacrifices informative content.

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 the simple operation but multiple parameters and no annotations or output schema, the description is too sparse. It fails to mention that host and port are likely connection parameters, and does not specify behavior on existing files or errors, making it incomplete for reliable invocation.

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 only 33% (only filepath is described). The description adds no additional meaning for host or port parameters, and does not elaborate on filepath beyond the schema's '.png' note. With low coverage and no compensatory explanation, parameter semantics are weak.

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 'Save VNA display screenshot' uses a specific verb ('save') and resource ('display screenshot'), clearly differentiating it from sibling tools like vna_save_touchstone (data file) and vna_save_state (state file). This makes the tool's purpose immediately apparent.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus vna_save_touchstone or vna_save_state, nor does it mention any prerequisites like connection requirements.

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