ensp_verify_ospf

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

With no annotations, the description carries the full burden, and it does disclose that two read-only `display` commands are run and their outputs are merged. However it says nothing about session requirements, whether the session must already be in system view, error behavior when OSPF is not configured, or how the merge is structured.

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 commands to be executed are stated immediately. It is terse to the point of omitting needed parameter/usage detail, but no sentence is wasted.

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 presence of an output schema means return-value semantics need not be described, and the tool is a simple two-command reader. Still, with zero schema description coverage, no annotations, and no usage guidance, the definition is only minimally complete for an agent to invoke it confidently.

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 is expected to compensate, yet it adds no information about the single `session_id_or_name` parameter. The parameter name is fairly self-explanatory, but whether an ID or a name is accepted and their format is left undocumented in both schema and description.

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 names a specific action (execute the two OSPF display commands) and the exact resources involved (`display ospf peer brief` and `display ospf routing`), so an agent knows precisely what the tool does. It does not explicitly distinguish itself from the adjacent `ensp_verify_routes` sibling, which is the only missing clarity element.

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?

Usage is only implied via the tool name and the OSPF-specific commands listed; there is no statement of when to prefer this over `ensp_verify_routes` or the generic `ensp_send_command`/`ensp_verify_interfaces` tools. No prerequisites or exclusions are given.

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