retrieveHandlesAuditsListList history about your handles (audit) - List and filters the history about your handles.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| size | No | ||
| endDate | No | ||
| orderBy | No | ||
| handleId | No | ||
| changedBy | No | ||
| requestId | No | ||
| startDate | No | ||
| x-trace-id | No | ||
| x-request-id | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / x-hapi-auth-stateRemoved value: -{
- "type": "string"
-}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this as a safe read-only operation; the description adds only 'filters' and 'audit', which are purpose-level. It fails to disclose pagination behavior, default result size, ordering, or what the history entries contain.
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 one sentence but redundant, repeating 'List history about your handles' twice. It is short but wastes a full clause on restating the title, leaving no room for useful detail.
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?
With 10 parameters, no output schema, and no usage or parameter guidance, this description is wholly inadequate for invoking the tool correctly. The bare 'audit' mention does not explain what is returned or how filtering works.
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 coverage is 0% across 10 parameters, and the description offers no parameter-specific meanings. 'Filters' is too generic to explain page, size, orderBy, handleId, changedBy, date ranges, or request IDs.
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 title and description clearly identify the tool as listing audit history for handles, using the specific verb 'List' and resource 'history about your handles'. The 'audit' qualifier distinguishes it from sibling tools like listHandles/retrieveHandle, though it doesn't explicitly name alternatives.
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. The description only restates the action and mentions filters, without specifying scenarios, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.