vna_clear_port_extension

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. It merely restates the named action without mentioning side effects, whether the operation is reversible, or if vna_port=0 applies to all ports (though this is in the schema). This leaves key behaviors untold.

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, concise phrase that is appropriately short for a simple tool and front-loads the action. It lacks structured detail but does not waste words, earning a strong score.

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 is simple, but the description is incomplete for an agent. It omits behavioral context such as prerequisites (e.g., connection), effect on existing port extensions, and the relationship to vna_set_port_extension. With no output schema and no annotations, the description should provide more 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?

Schema description coverage is only 33% (only vna_port has a description), and the tool description adds no parameter details. It does not explain 'host', 'port', or clearly map 'specified port' to a specific parameter, so it fails to compensate for the low schema coverage.

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 'Clear/disable port extension for specified port' provides a specific verb-resource pair and is easily distinguishable from sibling tools like vna_set_port_extension or vna_get_port_extension. However, 'specified port' is ambiguous, as it could refer to either the 'port' or 'vna_port' parameter, preventing a perfect score.

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 guidance is given on when to use this tool versus alternatives, nor are any prerequisites or context provided. The description simply states the action without explaining scenarios where clearing/disable is appropriate.

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