Create a new SecIntel profile group to organize threat intelligence profiles, enabling grouped management and assignment of security intelligence settings within Security Director Cloud.
Create a new SecIntel profile group 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 provided, so the description must fully disclose behavior. It only states the creation action, but does not mention idempotency, error conditions, required permissions, or any side effects. The lack of behavioral context is a significant gap.
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 directly relevant and front-loaded with the key action. No unnecessary words or details are present.
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 complexity (nested object body, no output schema, and a generic schema description), the description is woefully incomplete. It does not explain what a SecIntel profile group is, expected fields, or what the response contains, making it insufficient for reliable agent use.
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 a single required parameter 'body' with a generic description. Schema description coverage is 100%, so the baseline is 3. The tool description adds no additional meaning for the parameter, and the schema description is vague ('matching the target Security Director Cloud schema').
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 'Create a new SecIntel profile group object.' The verb 'Create' and the resource 'SecIntel profile group' are specific, and the tool is clearly distinguished from sibling tools like get, update, delete, list for the same resource, as well as create for individual profiles.
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 provides no guidance on when to use this tool versus alternatives such as updating or listing profile groups. There is no mention of prerequisites, expected context, or conditions for creation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.