Detect tampering in an agent's action log by auditing sequential cryptographic checksums and confirming the audit trail remains unaltered.
Audits sequential cryptographic checksums to ensure audit log has not been altered.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | Agent ID whose action log history will be verified | |
| audit_depth | No | Number of recent log events to verify (default 50) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the method (cryptographic checksums) but does not state whether the operation is read-only, what happens on verification failure, or any side effects. For a verification tool, this is a significant gap that leaves the agent guessing about the result format and error behavior.
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?
A single, tightly written sentence that front-loads the core verb and purpose. No redundant words or filler.
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 two-parameter tool, the description is adequate in scope, but because there is no output schema, the description should clarify what the tool returns (e.g., a boolean, a report, or an error) and whether it is safe to call repeatedly. This omission makes it slightly incomplete for an agent deciding how to handle the result.
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%, so both parameters (agent_id and audit_depth) are already documented in the input schema. The tool description adds no additional meaning about parameters, so the baseline of 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?
States a specific verb (audits) and resource (audit log) with a clear intent (ensure not altered). It is unambiguously distinct from the sibling 'record_agent_action', which writes entries rather than verifying them, so an agent can tell them apart immediately.
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?
Provides clear context for when to use the tool (verifying log integrity) and implicitly that it is for verification, not recording. However, it does not explicitly name the sibling or give when-not conditions, so it falls short of a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.