vna_output_off

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

With no annotations, the description carries the full burden. It states the action (disable RF output) and calls it 'safe state', but does not disclose side effects, reversibility, prerequisites, or impact on ongoing operations. This adds minimal value beyond the name.

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, front-loaded phrase with zero wasted words. It sacrifices detail for brevity, but for the action it conveys, it is appropriately concise, though it omits any discussion of parameters or edge cases.

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?

For a tool with two undocumented parameters and no annotations, this description is incomplete. It does not explain what host and port refer to, what 'safe state' means, or what happens after disabling. The absence of output schema details further limits context.

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?

The schema has 0% description coverage for the host and port parameters, and the description does not mention them at all. This leaves agents without any guidance on what values to supply, offering no compensation for the schema gaps.

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 'Disable' and resource 'RF output', clearly distinguishing it from the sibling tool vna_output_on. The parenthetical '(safe state)' adds context that this is a deliberate safety action.

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 explicit when-to-use guidance or alternatives are provided. While the name and 'safe state' hint at safety contexts, the description does not explain when to prefer this over vna_output_on or other tools.

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