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

No annotations are provided, so the description carries the full burden. It implies a read-only reference operation ('Read it before you write') and discloses some domain rules (authority lattice, verified condition), but it does not explicitly state that the tool has no side effects or describe what it returns in terms of structure or format. The warning about system errors adds context but is ambiguous.

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 description is a single, dense paragraph that packs in a clear headline, an enumerated list of contents, and usage warnings. Every sentence contributes value, but the stylistic 'THE GATE KERNEL' and the cryptic phrasing ('the law you keep here') could be more straightforward. It is not overly long and is front-loaded with the purpose.

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?

Given zero parameters and no output schema, the description is sufficiently complete: it explains what the tool contains, when to use it, and key rules. It lacks an explicit statement of return type or behavior (e.g., 'this is a read-only fetch'), but for a zero-parameter reference tool, the context 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 has zero parameters, so the description does not need to explain parameter semantics. The schema is empty and the description adds context about the content that will be retrieved, fully compensating for the absence of parameters.

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 clearly identifies the tool as 'THE GATE KERNEL' and states it provides 'the law you keep here, in one call', enumerating specific contents (five moves, eight-rule covenant, six KINDS, authority lattice, nine-field gate record). This gives a specific verb+resource sense (retrieve the kernel rules), though it does not explicitly differentiate from sibling tools like 'kernel_gate' or 'canon'.

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 description gives explicit usage guidance: 'Read it before you write' — indicating this tool should be consulted prior to any write operation. It also provides interpretive guidance ('a system error is never a false verdict') and a condition for verification ('only a witnessed, evidenced gate reaches verified'). However, it does not name alternative tools or state when not to use it.

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