nodesAddFabricNodes

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

No annotations are provided, so the description carries full burden. It states this is an 'Add' operation, implying a write/mutation, but doesn't disclose any behavioral traits: no mention of permissions required, whether it's idempotent, if it validates input, what happens on failure, or what the response contains. For a mutation tool with zero annotation coverage, this is a significant gap.

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 brief and front-loaded with the core purpose. The second sentence is somewhat redundant with the schema but provides a minimal usage example. No unnecessary words, though it could be more informative given the complexity of the tool.

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 tool's complexity (adding nodes to a fabric with nested objects), lack of annotations, and no output schema, the description is incomplete. It doesn't explain the fabric context, what happens after addition, error conditions, or relationship to other node tools. For a mutation tool in a networked system, this leaves critical gaps.

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 100%, so the schema fully documents both parameters (fabricId and nodes). The description adds no meaning beyond what the schema provides—it doesn't explain what a 'fabric' is, clarify the relationship between fabricId and nodes, or provide examples beyond a generic syntax hint. Baseline 3 is appropriate when the schema does all the work.

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 the action ('Add') and resource ('one or more nodes'), but it's vague about what 'nodes' are in this context. It doesn't differentiate from sibling tools like 'nodesAddManagementPorts' or 'nodesAddNodeLoopbacks', which also add things to nodes. The purpose is understandable but lacks specificity about the domain (fabric networking).

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 on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing fabric), exclusions, or related tools like 'nodesUpdateFabricNode' or 'nodesDeleteFabricNode'. The second sentence is about parameter syntax, not usage context, so it offers no real guidelines.

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