vna_get_port_extension

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

The description adds the behavioral detail that port extension settings include delay and loss compensation, giving insight into the return content. However, without annotations, it does not explicitly state that this is a read-only operation, whether it requires an active connection, or any side effects. The verb 'Get' implies read-only, but more explicit disclosure would be better.

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?

Single concise sentence that is front-loaded with the operative verb and resource. No wasted words, and the parenthetical adds necessary specificity about the settings without verbosity.

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 annotations, no output schema, and incomplete parameter descriptions. The description only states what the tool retrieves but does not explain host/port parameters, prerequisites, return format, or error conditions. For a getter tool, more context about the connection and result structure is needed.

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). The tool description does not add meaning for host or port parameters, and only indirectly relates to vna_port via the 'delay and loss compensation' detail. 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 'Get port extension settings (delay and loss compensation)' uses a specific verb 'Get' and names the exact resource (port extension settings) with detail on what they include. This clearly distinguishes it from sibling tools like vna_set_port_extension and vna_clear_port_extension.

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 provided on when to use this tool versus alternatives. There is no mention of prerequisites, connection state, or situations where this tool would be preferred over other getter tools.

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