Transforms a detected threat pattern into a non-executing defensive antibody recipe, giving security teams a concrete countermeasure for matching fleet signals before any action is taken.
Synthesize a non-executing defensive antibody recipe from a threat pattern.
| Name | Required | Description | Default |
|---|---|---|---|
| pattern | Yes | ||
| signals | Yes |
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 the burden. The qualifier 'non-executing' is a useful behavioral disclosure, indicating the tool produces a recipe rather than taking action. However, it does not say whether the operation is read-only, whether it has side effects, or what the output recipe contains.
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 efficient sentence that front-loads the verb, object, and key qualifier. No filler or redundant 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 complex nested input schema, no annotations, and no output schema, a single sentence is not enough. The description omits usage context, parameter details, output format, and behavioral edge cases, so an agent cannot reliably call it correctly without additional inference.
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?
Schema description coverage is 0%, so the description must compensate. It only hints at 'pattern' as a threat pattern; the required 'signals' parameter and all nested fields are left unexplained. This is minimal semantic value.
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 states a specific verb ('Synthesize') and resource ('non-executing defensive antibody recipe') and names the input source ('from a threat pattern'). It clearly conveys what the tool produces, though it does not explicitly compare with sibling tools.
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 given on when to use this tool instead of immune_discover, immune_cycle, immune_crystallize, immune_recall, or immune_breed. The only hint is 'from a threat pattern,' which is not enough to select among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.