verify_audit_log

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It discloses the verification mechanism (hash-chain) and the classes of anomalies it can detect, which is meaningful context, but it does not state that the operation is read-only/non-mutating, whether it requires elevated permissions, or whether cryptographic verification is expensive or long-running over a large ledger.

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 compact sentence with the core action front-loaded and no filler. Every clause (mechanism, target, detected anomalies) 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 one-parameter tool this is close to adequate, but with no output schema the description should hint at what a verification result contains (pass/fail, offending record index, proof details). It also omits the important scoping caveat implied by 'limit' — that only recent records are checked, so tampering further back could be missed.

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%, and the single 'limit' parameter is fully documented in the schema as 'Number of recent audit records to verify.' The description adds no semantics about the parameter (e.g., that verifying only a subset leaves earlier ledger history unchecked), 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 names a specific verb and mechanism ('cryptographically verifies') applied to a specific resource ('immutable hash-chained audit ledger') and states the outcome ('detect tampering, deleted records, or unauthorized log modifications'). This is far more than a restatement of the name, but it never references any sibling tool (e.g., get_security_posture, inspect_payload_dlp) to help the agent route between them.

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 invoke this versus alternatives such as get_security_posture or inspect_payload_dlp, and no mention of prerequisites or when verification is unnecessary. The description is purely declarative about what the tool does, leaving the selection decision entirely to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.