Update tenant-wide firewall global settings to enforce consistent security defaults across the organization. Apply a single configuration to all firewalls.
Update the tenant-wide firewall global settings singleton.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON request body matching the target Security Director Cloud schema. |
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, so the description carries full burden. It indicates mutation ('Update') but does not disclose whether the update is destructive or merging, required permissions, or other behavioral effects. The body parameter is a generic object with no schema details, leaving behavior ambiguous.
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 sentence with no wasted words. However, it could be improved by adding structure or a brief list of key points. As is, it is efficient but somewhat minimal.
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 absence of an output schema and annotations, the description is incomplete. It does not explain what 'global settings' include, what fields are expected in the body, or any side effects. A mutation tool with a generic body parameter requires more context for safe and effective use.
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 input schema has 100% coverage but the description of the 'body' parameter is generic ('JSON request body matching the target Security Director Cloud schema'). It adds no specific meaning about the required fields, format, or constraints beyond the schema, which is insufficient for a nested object parameter.
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', the resource 'firewall global settings', and specifies 'tenant-wide' and 'singleton'. It distinguishes from siblings like sdcloud_get_firewall_global_settings and sdcloud_set_firewall_global_profiles.
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 when updating tenant-wide global settings, but provides no explicit guidance on when to use this tool versus alternatives (e.g., when to use sdcloud_set_firewall_global_profiles instead) or any prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.