Create per-device firewall global settings to configure device-specific security parameters and manage firewall behavior in Security Director Cloud.
Create a new per-device firewall global settings object.
| 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 provided; the description only says 'Create a new... object' without disclosing behavioral traits like idempotency, overwrite behavior, auth requirements, or side effects.
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 one sentence and concise, but it omits necessary information such as parameter details and usage context. Conciseness without completeness is not ideal.
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 no annotations, no output schema, a single parameter with a vague description, and many siblings, the description is inadequate for proper tool selection and invocation. It lacks detail about required body structure, constraints, and return value.
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% (body has a description), so baseline is 3. The description adds no extra meaning beyond what the schema provides; it simply restates 'matching the target schema' without detailing fields.
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 ('Create') and the resource ('per-device firewall global settings object'). It distinguishes from siblings like update, delete, list, and get, and from global settings tools by specifying 'per-device'.
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 provided on when to use this tool versus alternatives (e.g., update, set_firewall_global_settings). No prerequisites, when-not, or context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.