Create a new identity object with name, description, identity type, and domain to define users or groups for Security Director Cloud policy enforcement.
Create a new identity object. Body typically includes name, description, identity_type, identity_domain.
| 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 burden for behavioral disclosure. It only states the creation action but does not mention any side effects, permissions required, idempotency, or constraints. The description lacks important context despite the tool being a mutation.
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?
Two short sentences with no unnecessary words. The purpose is front-loaded and the typical fields are provided efficiently. Every sentence earns its place.
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?
The description is incomplete for a create operation. It does not explain what the response contains (e.g., the created object ID), prerequisites (e.g., existence of identity_type or domain), or error conditions. Given no output schema, the description should provide more context.
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 schema only describes 'body' as a generic JSON object. The description adds value by listing typical fields (name, description, identity_type, identity_domain), which helps the agent construct the body. With 100% schema coverage but minimal schema detail, the description compensates well.
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 a new identity object') and lists typical fields (name, description, identity_type, identity_domain), making the tool's purpose unambiguous. It distinctly separates this create action from sibling tools like sdcloud_get_identity_object and sdcloud_update_identity_object.
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 is provided on when to use this tool versus alternatives, such as when to create vs. update an identity object. There are no prerequisites, exclusions, or context for when creation is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.