Update a security rule option by its UUID using a JSON body that matches the required schema, enabling precise modifications to firewall or NAT policy rule settings.
Update a rule option object by UUID.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON request body matching the target Security Director Cloud schema. | |
| uuid | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does 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 only states 'Update' but does not disclose whether the update is partial or full, idempotency, required permissions, or any side effects. This is insufficient for a mutation tool.
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 extremely concise, using a single sentence to convey the core purpose. No extraneous words, but it may be too brief to be fully informative. However, for a simple update operation, brevity is acceptable.
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 lack of output schema, annotations, and detailed parameter explanations, the description fails to provide enough context for effective tool use. It does not mention return values, error handling, or update semantics, leaving an agent with insufficient information to invoke the tool correctly.
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?
The description mentions the body parameter as 'JSON request body matching the target Security Director Cloud schema,' adding some context beyond the schema's minimal descriptions. However, it does not explain the structure or constraints of the body, and the uuid parameter is not elaborated. With 50% schema coverage, the description provides marginal added value.
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 (Update) and the resource (rule option object) with a specific identifier method (by UUID). It effectively differentiates from sibling tools like create, get, and delete, but is somewhat terse.
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 on when to use this tool versus alternatives such as create or delete. The description does not mention prerequisites, when to avoid using it, or any context for its typical use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.