Creates a new custom rights category in VCF Automation, defining its name, bundle key, parent, and rights counts to organize access control.
Create a new custom rights category. Creates a new custom rights category. POST /cloudapi/1.0.0/rightsCategories
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | RightsCategoryNode |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description primarily restates the API endpoint and the action. Annotations already clarify that this is a mutable operation (readOnlyHint: false), so the description provides only minimum viable context.
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 suffers from significant redundancy, repeating 'Create a new custom rights category' twice before including the full API path. This repetition wastes space and detract from structural efficiency.
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?
While the input schema is extremely detailed, the description itself is extremely brief. It fails to provide any high-level context about the business logic or the nature of the 'Rights Category' resource in the overall system.
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%, which establishes a baseline score of 3. The description offers no additional semantic meaning regarding the complex fields (like rightsCount or subCategories) that are defined in the schema.
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 and immediately states the action (Create) and the target resource (custom rights category). Given the extensive list of sibling tools, this purpose is highly distinct from query or delete operations.
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 explicit guidance on when to use this tool versus alternative methods (e.g., when to use a pre-existing category). Usage is only implied by the creation action.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.