Update an ungrouped firewall policy rule in Security Director Cloud by supplying policy UUID, rule UUID, scope, and JSON body to modify the rule's configuration.
Update an ungrouped firewall policy rule.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON request body matching the target Security Director Cloud schema. | |
| scope | Yes | Rule scope: 'global' or 'zone'. | |
| rule_uuid | Yes | ||
| policy_uuid | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only states 'update' without detailing behavioral traits such as idempotency, side effects, authorization needs, or response format.
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 a single concise sentence, but it is overly brief and lacks key details that would justify space saved.
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 (4 required params, nested body, no outpput schema or annotations), the description fails to explain the body format, required fields, or post-update behavior, leaving significant 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 50% (scope and body have descriptions; policy_uuid and rule_uuid do not). The tool description adds no parameter-level information to compensate for the gap.
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 verb 'update' and the specific resource 'ungrouped firewall policy rule', and distinguishes it from grouped rule updates via sibling tools like sdcloud_update_firewall_policy_rule_in_group.
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 implies usage for ungrouped rules but provides no explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like the grouped update tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.