vnisAddFabricVniMembers

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool adds members, implying a mutation, but lacks details on permissions, side effects, error handling, or response format. The syntax hint is minimal and doesn't cover critical operational aspects.

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, followed by a syntax example. Both sentences are relevant, with no wasted words. However, the example could be more precise (e.g., clarifying it's for illustration) to avoid potential confusion.

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 complexity of adding network members (a mutation operation), no annotations, and no output schema, the description is insufficient. It lacks information on success/error responses, idempotency, constraints (e.g., duplicate members), and how it integrates with sibling tools, leaving significant gaps for an AI agent.

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 the three parameters (fabricId, vniId, members). The description adds no additional semantic meaning beyond the schema, such as explaining relationships between parameters or usage nuances. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 ('Add') and resource ('one or more VNI members'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'vnisAddFabricVnis' or 'vnisDeleteFabricVniMember', which would require more specific context about what constitutes a VNI member versus a VNI itself.

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 provides no guidance on when to use this tool versus alternatives, such as 'vnisUpdateFabricVni' or 'vnisDeleteFabricVniMember'. It only offers a syntax example, which is helpful but doesn't address contextual usage, prerequisites, or exclusions.

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