ciso_assistant_api_cwes_batch_action_createPerforms a batch action on multiple CWE objects, letting you apply one operation across many items at once instead of updating each individually.
Perform a batch action on multiple objects.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.3.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true; the description adds nothing beyond that. It does not say what a "batch action" can do (field updates? folder assignment?), whether failures are partial, or that some batch operations may be irreversible despite destructiveHint=false.
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?
It is a single front-loaded sentence with no filler, but its brevity comes from under-specification rather than efficiency. Nothing in the sentence tells the agent anything the tool name did not already convey.
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 non-idempotent mutation endpoint with an empty parameter schema and no output schema, the description should explain the batch mechanism, required target list, and outcome. None of that is present, so an agent cannot reliably construct a correct call.
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 has zero parameters, which normally sets a baseline of 4, but here the empty object with additionalProperties=false is anomalous: the description gives no hint how the target object IDs and the action itself are supplied. That is a real gap the description should have compensated for, so it scores below the nominal baseline.
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 says only "Perform a batch action on multiple objects" – "objects" is undefined and the resource (CWEs) is never mentioned, so it reads as a restatement of the name/title. Dozens of sibling tools are also named *_batch_action_create, and nothing here distinguishes this one from them.
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?
There is no statement of when to use this tool, when to prefer the single-record cwes_create/cwes_update/cwes_partial_update, or which batch actions exist. The agent is left to infer everything from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.