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

No annotations are provided, so the description carries the behavioral burden. 'Read it before you write' implies a safe, side-effect-free read, but the description never states the return format, idempotency, or that it modifies nothing. The remaining text describes conceptual content rather than the tool's runtime 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?

The identity and the 'read before write' imperative are front-loaded, and the middle clause compactly lists the kernel's contents. It is dense with domain jargon, but each clause maps to real content rather than padding.

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 zero-param reference tool with no output schema and no annotations, the description usefully enumerates what the caller receives (five moves, covenant, KINDS, lattice, gate record). It omits the response format, but coverage of the payload content is adequate.

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 the baseline of 4 applies. Schema coverage is 100% and there are no arguments to mis-specify.

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 identifies a specific artifact ('THE GATE KERNEL — the law you keep here, in one call') and enumerates its contents (five moves, eight-rule covenant, six KINDS, authority lattice, nine-field record), so an agent knows this is a reference-fetch for the governance kernel. The action verb is implied ('read it', 'in one call') rather than stated, and it never names the sibling kernel_gate to differentiate scope.

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?

'Read it before you write' gives a clear usage context and ordering cue for when to call this relative to write operations. There are no explicit exclusions or named alternatives, but the precondition is unambiguous.

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