vna_trigger_sweep

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

No annotations are present, so the description carries the burden. It does disclose the key behavior of triggering and waiting for completion, but it lacks details on error handling, return value, or side effects. This is minimally adequate but not comprehensive.

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?

One concise, front-loaded sentence with no redundant words. It is appropriately sized for the simplicity of the action, and every word adds value.

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 no output schema or annotations, and the description is sparse. It does not explain what happens after completion (e.g., where results are stored), how it relates to data retrieval tools, or the behavior when timeout is exceeded. For an AI agent, this context is insufficient.

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 only 33% (only timeout has a description). The tool description does not elaborate on host, port, or timeout semantics, beyond what the schema already provides. Given the low coverage, the description should compensate but does not, leaving host/port meaning ambiguous.

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 uses a specific verb 'trigger' and resource 'single sweep', clearly distinguishing it from sibling tools like vna_configure_sweep or vna_get_s_parameter. The added 'wait for completion' states the blocking behavior, making the purpose unambiguous.

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 mention of prerequisites (e.g., connection, configured sweep), and no reference to sibling tools. It simply states what it does, leaving the agent to infer usage context.

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