vmware-nsx-security

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

With no annotations provided, description carries full burden and discloses return payload composition ('expression rules and up to 50 effective VirtualMachine members'). Does not mention error behavior (e.g., group not found) or auth requirements, but successfully describes output structure.

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?

Three sentences efficiently structured: purpose statement, return value disclosure, and Args documentation. No redundant information; front-loaded with action and resource type.

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?

For a 2-parameter retrieval tool without output schema, description adequately covers what gets returned. Minor gap regarding error handling or missing group behavior, but parameter semantics and return structure are well-documented.

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 has 0% description coverage, but description fully compensates by documenting both parameters: provides concrete example for group_id ('web-tier-vms') and explains target's purpose ('NSX Manager target name from config') and optionality.

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?

Specific verb ('Get') + resource ('security group') + scope ('membership criteria and effective members'). Clearly distinguishes from sibling 'list_groups' by specifying single-group retrieval and from 'create_group'/'delete_group' via the 'Get' verb.

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?

Implies usage through required group_id parameter and return description, but lacks explicit comparison to siblings like 'list_groups'. The 'up to 50 effective members' caveat hints at limitations but doesn't state when to use alternatives.

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