ciso_assistant_api_pmbok_responsibility_matrices_retrieveRetrieve a PMBOK responsibility matrix by ID, returning the record with unauthorized related fields masked.
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 establish that this is a safe, idempotent read. The description adds useful behavioral context by noting that unauthorized related fields are masked, but it gives no detail about what masking means for the caller or what permission conditions trigger it.
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 efficient sentence with no wasted words. However, the sentence is too generic to front-load the resource being retrieved.
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 retrieve-by-id endpoint with no output schema, the description should identify the object type and clarify the id semantics. It leaves those essentials to the tool name and says nothing about how this differs from the many sibling retrieve tools.
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 one required id parameter at 0% description coverage, and the description does not explain what the id identifies or what format it takes. It does not 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?
The description says it returns a single object, implying a read-by-ID retrieval, and mentions masking. But it never names the PMBOK responsibility matrix resource itself, so an agent must rely on the tool name to understand what is being retrieved.
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 tool rather than the sibling list, object_retrieve, or other responsibility-matrix endpoints. It also never states that the required id parameter selects the object.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.