list_models

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds useful context that results come from a static hardware catalog rather than the active topology, but says nothing about result size, paging, or ordering.

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?

Two sentences, front-loaded with the core action and followed by the filtering behavior. Slightly clause-heavy in the second sentence but no wasted filler.

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?

With an output schema present, return values need no explanation, and annotations cover the safety profile. Both parameters are addressed and the catalog-vs-live distinction is made, leaving little an agent needs beyond this to call it correctly.

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 100% so the baseline is 3, but the description goes further by giving concrete device-kind and module-kind examples (access_point, interface_card, pt_laptop_module) and, importantly, explaining the interaction: passing a module kind to `kind` lists only modules. That interaction is meaningful semantics 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?

States a specific verb and resource ("List the device models this Packet Tracer can create") and clarifies the source is the hardware catalog rather than live network state, which implicitly separates it from list_devices/list_slots. It does not explicitly name a sibling, so it stops short of full differentiation.

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?

Explains the two practical usage modes (filter by kind, or set include_modules/adjust kind to surface modules), which is implied guidance. However, it never states when NOT to use it or points to an alternative such as list_devices for currently instantiated hardware.

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