pve_sdn_fabric_nodes_list

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

The description declares READ-ONLY, ensuring safety, but lacks details on permissions, side effects, or pagination; with no annotations, more transparency would be helpful.

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?

Description is a single sentence, front-loaded with READ-ONLY, with no unnecessary words; perfectly concise.

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?

With an output schema present, description is nearly complete; it misses a mention of optional parameters (pending/running) but covers the core functionality.

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 coverage is 100%, so baseline is 3; description adds no extra meaning beyond the schema for parameters like pending, running, or proximo_target.

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 it lists nodes for ONE SDN fabric and is READ-ONLY, distinguishing it from siblings like pve_sdn_fabric_nodes_list_all.

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?

The description implies usage for a specific fabric but does not explicitly contrast with alternatives (e.g., pve_sdn_fabric_nodes_list_all) or provide when-to-use guidance.

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