pve_sdn_fabric_nodes_list_all

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

The description declares the tool as READ-ONLY and specifies it lists all nodes, but does not elaborate on additional behaviors such as how parameters like 'pending' and 'running' affect the output or any performance implications. With no annotations, more detail would be beneficial.

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 concise sentences, front-loaded with 'READ-ONLY', and no extraneous information. Every sentence adds value.

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?

Given the simplicity of the tool (a list call with optional filters) and the existence of an output schema, the description is sufficiently complete. It also explicitly contrasts with the sibling for clarity.

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 covers all parameters with descriptions (100% coverage), so the description adds no extra meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states the action ('list') and resource ('fabric node') and specifies the scope ('across EVERY fabric'), distinguishing it from the sibling tool pve_sdn_fabric_nodes_list.

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?

Explicitly tells when to use this tool (for all fabrics) and when to use the alternative (pve_sdn_fabric_nodes_list to scope to one fabric).

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