Deploy a firewall policy to a selected subset of its assigned devices. Provide the policy ID and request body to update only targeted devices.
Deploy a firewall policy to a selective subset of its assigned devices.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON request body matching the target Security Director Cloud schema. | |
| policy_id | 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, so the description must bear the full burden of behavioral disclosure. It only states 'selective subset' without explaining how the subset is determined, any side effects, or what happens to non-selected devices. There is no mention of required permissions, rate limits, or other behaviors.
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 that is concise and front-loaded with the core action. However, it sacrifices detail for brevity, which may not be optimal for a tool with nested parameters.
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 output schema, no annotations, and a required nested object parameter, the description is too brief. It fails to explain the structure of the body parameter, the meaning of 'selective subset', or any return values. Users would need to consult external documentation to use this 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?
Schema coverage is 50% (only 'body' has a description, 'policy_id' has none). The description does not add any meaning beyond the schema; it does not explain what the 'body' should contain or how to specify the subset. The body's description is generic and does not provide tool-specific context.
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 (deploy), the resource (firewall policy), and the specific scope (selective subset of assigned devices). This distinguishes it from the sibling 'sdcloud_deploy_firewall_policy' which likely deploys to all assigned devices.
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 does not provide any guidance on when to use this tool versus alternatives like the full deploy tool. No context is given about prerequisites, scenarios, or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.