ciso_assistant_api_pmbok_responsibility_matrices_object_retrieveRetrieves a specific PMBOK responsibility matrix by its ID from CISO Assistant, returning the assigned roles and responsibilities for project governance and stakeholder accountability.
api_pmbok_responsibility_matrices_object_retrieve
| 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, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on what the object contains, permission requirements, or 404 behavior on a bad id.
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 short, but only because it contains no information at all — an identifier echo rather than a front-loaded summary. Under-specification, not conciseness.
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 tool with no output schema and an undocumented id, the agent cannot tell what a 'PMBOK responsibility matrix' object is or how to obtain a valid id (likely via the _list or _object_retrieve siblings). The definition leaves the agent without enough to call it confidently.
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% for the single required 'id' parameter, and the description offers no compensating text about what the id refers to (matrix UUID? project-scoped ref?) or its format. With a low-coverage parameter, the description was the only place to explain it and it said nothing.
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 is simply the tool's snake_case identifier restated verbatim, which is a tautology rather than a statement of purpose. The name does encode 'retrieve PMBOK responsibility matrices object', so an agent can piece together a read-by-id operation, but the description itself contributes no verb-plus-resource phrasing or sibling differentiation.
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 indication of when to use this versus the many sibling retrieval tools (e.g. ciso_assistant_api_pmbok_responsibility_matrices_retrieve, _list, or the _object_retrieve variants on activities/actors). There is no exclusions, prerequisites, or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.