zyxel_show_spanning_tree

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

With no annotations, the description must fully convey behavioral context. It only says 'Display,' which implies a read-only operation, but gives no details about the output contents, potential side effects (e.g., requiring privileged mode), or limitations (e.g., only works on certain firmware versions).

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?

The description is a single, grammatically clear sentence with no unnecessary words or repetition. It is perfectly concise and 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 tool is relatively simple with two optional parameters, but the lack of an output schema means the description should clarify what 'Spanning Tree Protocol information' includes (e.g., root bridge, port states, timers). The current phrasing is vague and does not fully compensate for the absence of output schema or annotations.

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?

The input schema already provides descriptions for both parameters ('STP instance number' and 'Show STP info for specific interface'). The tool description adds no additional parameter-level meaning, so it receives the baseline score for high schema coverage.

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 clear action ('Display') and a specific resource ('Spanning Tree Protocol information'), uniquely identifying it among the many sibling show commands. It is immediately obvious what this tool does.

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?

No guidance is provided about when to use this tool versus alternatives such as other show commands. There is no mention of prerequisites, typical scenarios, or situations where a different tool would be more appropriate.

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