ensp_get_recent_output

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: it does not state that the operation is read-only, whether reading consumes or clears the buffer, whether long buffers are truncated, or that the session must already be connected. Only the notion of 'most recent' lines hints at trailing-window semantics.

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?

A single front-loaded sentence with no filler; the resource and the limiting parameter appear immediately. It is efficient, but the terseness is partly the reason behavioral and usage context is absent.

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?

A two-parameter tool with an output schema and zero annotation coverage needs more than one sentence. The description omits preconditions (connected session), buffer behavior, and any routing guidance, leaving the agent to infer how this fits with the dispatch/clear-output siblings.

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%, so the description must compensate. It does clarify the `lines` parameter by naming it and framing it as the count of most-recent lines (the schema alone only says 'integer, Lines'), but the required `session_id_or_name` parameter is never explained — thankfully its name is largely self-describing.

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 (获取/get) and resource (会话输出缓冲/session output buffer), with the scope limited to the most recent lines. This is enough to separate it from ensp_get_running_config or ensp_clear_output_buffer, though it never names those alternatives explicitly.

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?

There is no when-to-use or when-not-to-use guidance. Nothing tells the agent whether this is meant to be called after ensp_send_command, whether it should be used instead of a verify_* tool, or what happens relative to ensp_clear_output_buffer.

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