Create an exempt rule in an IPS profile to exclude specific traffic from intrusion prevention inspection, simplifying policy management.
Create an exempt rule within an IPS profile.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON request body matching the target Security Director Cloud schema. | |
| profile_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 provided, so description carries full burden. Only states 'Create an exempt rule' with no disclosure of authorization needs, side effects, idempotency, or error conditions.
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?
Extremely concise single sentence, but under-specified. Lacks important details that would aid agent understanding.
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?
No output schema, no annotations, complex body parameter. Description fails to explain what an exempt rule is, body structure, or relationship to other IPS profile tools.
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?
Description adds no parameter information. Schema has 2 params, but `profile_uuid` is undefined and `body` description is generic. Schema coverage is 50%, description does not compensate.
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?
Clearly states the action 'Create', the resource 'exempt rule', and the parent context 'within an IPS profile'. Differentiates from sibling `sdcloud_create_ips_profile_rule` which creates a regular rule.
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 prerequisites, when to use vs alternatives, or exclusions. Does not mention that an IPS profile must exist first.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.