Recompute the audit hash chain; anchor head outside the database

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds genuine value by disclosing the two-part behavior (recompute chain, anchor head externally), which tells the agent this is an integrity-verification pass with an out-of-DB write to an anchor. The gap: it doesn't say whether the recompute is expensive, whether it can fail/abort, or what the outcome indicates.

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 front-loaded clause states the action and the key behavioral detail, with the endpoint in parentheses for traceability. No filler, no restatement of the title.

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 no parameters and no output schema, the description carries the burden of explaining what comes back from a verification call — e.g., a validity/chain-intact result or head hash — and it stops short of that. What it does say (recompute + external anchor) is accurate and sufficient to invoke it correctly, but not to interpret 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Nothing in the text muddies the empty schema.

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 resource ("Recompute the audit hash chain") plus the distinctive behavior of anchoring the head outside the database, which separates it from read-only listings like audit_list or members_audit. It doesn't explicitly name a sibling to rule out, but the operation is unmistakably encryption/integrity verification rather than a data listing.

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?

The purpose implies the usage context (verifying chain integrity/tamper evidence), but there is no explicit "use when..." statement, no mention of prerequisites such as required role, and no exclusion pointing at audit_list for plain log retrieval. An agent can infer the scenario but is not told it directly.

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