ensp_verify_lldp_neighbors

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

With no annotations, the description carries the full burden and does so richly: it documents the auto-enable state machine (detect disabled LLDP by keywords → system-view/lldp enable → wait → recollect), the failure path (second failure returns status=error with hint), the flag semantics of lldp_was_enabled/auto_enable_attempts, and interface-name normalization. This is deep behavioral disclosure beyond any structured field.

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?

Front-loaded with the core purpose and the sibling distinction, and the auto-enable logic is broken into numbered steps that are easy to follow. It is somewhat long, and the trailing code reference to grbj_ensp_mcp.lldp_verifier adds little for an agent caller.

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?

For a 4-parameter verification tool with an output schema, it covers everything needed: selection rationale, the auto-enable workflow, failure semantics, and even a preview of the returned fields. Nothing required to call it correctly is missing.

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 explains auto_enable and enable_retry_delay well (including the seconds-wait behavior), and detail is inferable from the 'brief vs full' command branch. However it never names detail or session_id_or_name explicitly, leaving the mapping partly implicit, so it falls just short of full compensation.

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: collecting LLDP neighbor information (真实物理连接) from a named device. It explicitly distinguishes itself from the sibling ensp_verify_interfaces by contrasting what each can see (local interface state vs. remote device+interface). An agent can pick the right tool without opening either schema.

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?

Gives explicit when-to-use context (run once per router/switch, then feed results to ensp_cross_validate_topology) and an explicit conditional alternative (auto_enable=False reverts to collect-only for scripts where LLDP is already enabled manually). The ensp_verify_interfaces comparison further routes selection.

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