ciso_assistant_api_presets_retrieveRetrieve a single preset by ID from CISO Assistant, with unauthorized fields masked in the returned object.
Return a single object with unauthorized related fields masked.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
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, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that unauthorized related fields are masked, which is useful behavioral context beyond annotations, but it does not explain auth requirements, error behavior, or other relevant traits.
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 with no wasted words, but it is not front-loaded around the actual action or resource. It leads with return behavior rather than stating 'retrieve a preset by id'.
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 simple retrieve-by-id tool, the description should at least identify the resource and the id parameter. It instead only describes masked return fields, leaving the core purpose and parameter semantics incomplete despite the annotations covering read safety.
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 single required 'id' parameter has 0% schema description coverage and the description does not mention it at all. The schema shows it is a required string, but the description adds no meaning about what id refers to or how it is used.
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 only says 'Return a single object with unauthorized related fields masked.' It never states that the object is a preset or that retrieval is by id, so the actual resource and operation must be inferred from the tool name. It is more informative than a tautology but still vague about purpose.
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 versus siblings such as ciso_assistant_api_presets_list, ciso_assistant_api_presets_object_retrieve, or other retrieve tools. The description provides no conditions, exclusions, or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.