List GRC compliance policies and their current status. Filter by state (draft, published, retired) to support compliance audits.
List GRC compliance policies and their current status
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max records (default 25) | |
| state | No | Filter by state (draft, published, retired) |
Changes observed during successful MCP inspections.
v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds that the tool returns 'current status', which is useful context. However, it does not disclose pagination behavior, ordering, or what 'current status' entails. No contradiction with annotations.
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 clear sentence, front-loaded with the verb, and contains no redundant information. It earns its place.
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 list tool with fully documented parameters and read-only/open-world annotations, the description is largely sufficient. It could mention default behavior or how to use the state filter, but the schema covers parameters and the description clearly names the resource and output focus.
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 100%: limit and state both have clear descriptions. The tool description adds no additional parameter semantics beyond what the schema provides, so the baseline 3 applies.
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 uses a specific verb ('List') and resource ('GRC compliance policies'), and adds 'their current status' to clarify the output includes status. This distinguishes it from sibling tools such as list_grc_risks, list_grc_controls, and get_compliance_assessment.
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 provided on when to use this tool versus alternatives. It does not mention which scenarios call for list_compliance_policies instead of list_grc_risks or list_audit_results, nor does it note any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.