list_models

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

With no annotations, the description carries the transparency burden and does disclose the optional topo_path consistency-check behavior. It does not explicitly state that the operation is read-only, although the wording '列出' and '核对' strongly imply no mutation.

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 concise and front-loaded with the main purpose, followed by usage context and parameter details. It avoids unnecessary verbosity while still conveying actionable guidance.

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 the simple three-optional-parameter interface and no annotations, the description is complete enough for an agent to decide when to call the tool and what to expect. It also ties the output to the sibling topo_connect workflow.

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?

Although the input schema has no parameter descriptions, the tool description compensates by explaining all three parameters: category values and blank behavior, model filtering and full-interface-list behavior, and topo_path validation behavior.

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 clearly identifies the tool's purpose: listing eNSP-supported device models and their interface inventories. It also distinguishes the tool from sibling topology operations by positioning it as the pre-topology lookup for model and port names.

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?

It explicitly says to call this before building a topology and that fromPort/toPort values in connection operations should use the interface names returned here. The parameter-specific guidance for category, model, and topo_path makes when and how to use the tool clear.

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