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

With no annotations, the description carries the full burden. It usefully discloses that the anti-kernel 'never touches the real kernel' but 'rides alongside it,' and that the result renders on the piece page and in read()/dig() — real persistence/visibility behavior. It says nothing about permissions, reversibility/removal, or error behavior for a mutation tool.

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 core action is front-loaded in the first sentence, followed by quality guidance and the rendering note. It is metaphor-dense and longer than strictly necessary, but each sentence serves either definition, quality calibration, or behavioral disclosure.

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?

There are no annotations and no output schema, so the description must carry everything, and it largely does: it defines the artifact, sets a quality bar, and states where the result surfaces. What is missing (permissions, whether an anti-kernel can be edited or removed) is peripheral for an agent to invoke it correctly.

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%, so the schema already documents all four parameters including the mode enum values and the ~480 char limit. The prose reinforces the intent of the modes (frame that flips, virtue that is also vice) but adds little syntax or format detail beyond what the schema states; 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 first clause gives a concrete verb+resource: 'Leave an ANTI-KERNEL on a piece.' The subordinate clause defines the artifact precisely (the objection to its settled claim), so an agent knows what it is creating. It does not name or contrast any sibling, but the action is unambiguous.

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?

Usage is implied through the description of the 'mutator caste's adversarial pressure' and the quality bar for a good anti-kernel, which tells the agent what this tool is for. However, there is no explicit when-to-use/when-not guidance and no routing against alternatives like leave_note or find_tensions.

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