Create a flow-based antivirus profile to define inspection settings for traffic flows in Security Director Cloud. Use it to configure antivirus protection for firewall policies.
Create a new flow-based antivirus profile 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 are present, so the description must carry the full burden. It does not disclose side effects (e.g., does it overwrite? is it idempotent?), required permissions, or any constraints. The minimal text offers no behavioral insight beyond the atomic action.
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 short sentence, which is concise but lacks structure. There is no front-loading of key information or separation of concerns. It is under-specified for the tool's complexity.
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 lack of output schema and a generic input schema, the description should offer richer context (e.g., what a flow-based antivirus profile is, typical use, relationship to other profiles). It fails to do so, leaving the agent without enough information to use the tool effectively.
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% but the only parameter 'body' has a generic description ('JSON request body matching the target Security Director Cloud schema') that adds no concrete meaning. The description does not explain required or optional fields, examples, or structure, leaving the agent to guess.
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 'flow-based antivirus profile object', distinguishing it from sibling tools that list, get, update, or delete. However, it lacks additional detail about what such a profile entails or why an agent would choose this over other create tools.
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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives (e.g., updating an existing profile), nor does it mention prerequisites or typical scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.