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

No annotations are provided, so the description carries the full burden. 'Deterministic' is a useful hint about reproducibility, but the description never says what it returns (pass/fail? report?), whether it needs specific input formatting, or what happens on failure. It also doesn't clarify how a deliverable and a spec are supplied when the schema declares no properties.

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 sentence that names the operation, the determinism trait, and the four check dimensions with no filler. It is efficient, though the parenthetical list slightly crowds the core statement.

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 output schema and no annotations, the definition should say more about return values and the relationship between this tool and the sibling quality/audit tools. As written, an agent can guess the purpose but not predict the response or the required invocation shape.

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 schema is an empty object with additionalProperties=true, yet the description implies two inputs (a deliverable and a spec) that are nowhere represented or documented. The parameter surface is therefore left ambiguous despite the nominal zero-parameter baseline.

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 states a clear verb+resource: a deterministic quality check of a deliverable against a spec, and it enumerates the check dimensions (length, coverage, honesty, structure). It does not, however, distinguish this from sibling tools like attest_quality or honesty_audit, which sound closely related.

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 use this tool versus attest_quality, honesty_audit, or audit_opportunity. The agent is left to infer the routing from names alone, and no prerequisites or exclusions are stated.

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