Create an SSL proxy profile to specify SSL type and preferred cipher, enabling secure SSL traffic inspection in firewall policies.
Create a new SSL proxy profile object. Body typically includes name, description, ssl_type, preferred_cipher.
| 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?
With no annotations, the description carries full responsibility for behavioral disclosure. It does not explain whether creation is immediate or async, required permissions, return value on success, or error handling. This lack of behavioral context leads to a low score.
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 concise (two sentences) and front-loaded with the core purpose. Every word adds value, with no redundant or extraneous information.
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 tool's simplicity (create operation) and lack of output schema or annotations, the description is insufficient. It fails to mention return values, error conditions, prerequisites, or whether the operation is synchronous. The open schema further necessitates more context, which is absent.
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 only one parameter 'body' with a generic description ('JSON request body matching the target Security Director Cloud schema'). The tool description adds value by listing example fields (name, description, ssl_type, preferred_cipher), guiding the agent on what to include. This improves parameter semantics beyond the schema alone.
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 tool's purpose: 'Create a new SSL proxy profile object.' It specifies the action (create) and resource (SSL proxy profile), and lists typical body fields (name, description, ssl_type, preferred_cipher), distinguishing it from sibling tools like list, get, update, and delete.
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 use for creation but does not explicitly state when to use this tool versus alternatives (e.g., update or delete). The verb 'create' provides clear context, but no exclusions or alternative scenarios are mentioned, resulting in a score of 4.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.