ciso_assistant_api_pmbok_responsibility_matrices_cascade_info_retrieveRetrieve cascade preview details for a PMBOK responsibility matrix by ID to see how responsibility entries propagate across related items.
Cascade preview:
| 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=true, idempotentHint=true, destructiveHint=false, so safety is covered structurally. The description adds only the vague notion of a "cascade preview", without saying what cascades, what the preview contains, or whether it reflects pending uncommitted changes.
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 brief, but brevity here is under-specification rather than economy: a two-word fragment with a trailing colon is not a front-loaded explanation of anything.
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?
Placeholder
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 parameter "id" has 0% schema description coverage, and the description does not say what kind of object the id identifies (a matrix? a project? an actor?) or what happens if it is unknown. The description fully fails to compensate for the schema gap.
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?
"Cascade preview:" is a fragment that restates a slice of the tool name without a verb or a resource. An agent cannot tell from this whether the tool returns a preview object, a list of affected objects, or a dry-run of a cascade delete.
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 guidance on when to use this rather than the sibling responsibility_matrices_retrieve or object_retrieve endpoints, nor on what prerequisites or side effects apply. Nothing tells the agent which situation selects this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.