Create an anti-spam profile to define email filtering settings that block unwanted messages and protect your network from spam threats in Security Director Cloud.
Create a new anti-spam 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 provided, and the description does not disclose behavioral traits. It fails to mention if the tool is idempotent, what happens if a profile already exists, authentication requirements, or any side effects. The description is silent on these aspects.
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, concise and front-loaded with the action. No unnecessary words, but excessively brief given the tool's complexity. It could include more detail without being verbose.
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?
For a CRUD tool with no output schema and no annotations, the description is incomplete. It omits information about response structure, error conditions, required body fields, and typical usage patterns, leaving the agent with insufficient context for reliable invocation.
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 only parameter 'body' is described in the schema as 'JSON request body matching the target Security Director Cloud schema,' which is vague and unhelpful. The tool description adds no additional meaning about required fields, structure, or constraints, failing to compensate for the schema's poor description.
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 explicitly states 'Create a new anti-spam profile object,' clearly indicating the verb ('Create') and resource ('anti-spam profile object'). It distinguishes itself from sibling tools like sdcloud_update_anti_spam_profile, sdcloud_delete_anti_spam_profile, etc., which are apparent from sibling names.
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 when to use this tool versus alternatives. It does not mention prerequisites, typical scenarios, or whether to use update instead of create for existing profiles. The description lacks context for appropriate use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.