ensp_scanTelnetPorts

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

With no annotations, the description must disclose behavior. It only mentions scanning TCP ports but lacks details on methodology (e.g., SYN scan), output format, behavior on timeout or closed ports, or prerequisites like eNSP running.

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 sentence, no redundancy. Every word contributes to the core purpose. Appropriate length for the tool's simplicity.

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 no output schema and 4 undocumented parameters, the description is insufficient. It lacks explanation of output, scanning behavior, and relationship to sibling tools like ensp_telnetConnect. A more complete description would include what results look like and preconditions.

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 0%, so description must add meaning. It mentions the port range but does not explicitly link 'startPort' and 'endPort' to the range, nor explain 'host', 'timeoutMs'. The description adds minimal semantic value beyond the schema.

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 explicitly states the verb 'scan', the resource 'local eNSP device Telnet/console TCP ports', and the typical port range. It clearly distinguishes from siblings which are configuration or connection tools.

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 implies usage for scanning ports before connecting, but does not provide explicit guidance on when to use this tool versus alternatives like ensp_telnetConnect. No when-not or prerequisites are mentioned.

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