ensp_get_device_info

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

With no annotations, the description carries the burden and does disclose real behavior beyond the schema: results are cached, and refresh=True triggers an actual `display version` execution on the device. It leaves out prerequisites (established session), failure behavior for an unreachable device, and any latency/rate considerations, so it is above average but not complete.

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 short sentences, no filler; the tool's output fields come first and the refresh/cache semantics follow, so the most important information is front-loaded.

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 description need not explain return values since an output schema exists, and it covers the returned fields plus the refresh trade-off. The main gaps are the unexplained required session identifier and the unstated requirement that a device session must already be connected.

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 0% for two parameters. The description fully explains `refresh` (re-run display version vs. return cache), which is genuinely valuable, but says nothing about `session_id_or_name` — the required identifier — so it only partially compensates for the coverage gap.

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 states a specific verb and resource (get device metadata) and enumerates the returned fields — hostname, model, version, uptime — which is enough to distinguish it from siblings like ensp_get_running_config. It does not explicitly name or route against a sibling, so it stops short of a 5.

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 only conditional given is internal to the tool: refresh=True re-runs `display version`, otherwise cached values are returned. That is useful parameter guidance but not when-to-use-this-vs-alternatives guidance; there is no mention of prerequisites such as an active session or when to prefer this over ensp_send_command.

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