keystone_harness_bootstrap

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

The description discloses idempotency ('Idempotent'), no-overwrite behavior ('never overwritten'), and that existing items are reported in `skipped`. With no annotations to fall back on, this fully covers the behavioral contract.

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?

Three compact, front-loaded sentences deliver purpose, behavior, and parameter guidance without waste. Every clause adds distinct information (created artifact, idempotency, usage, parameter implications).

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 single-parameter bootstrap tool, the description covers what, when, why, and parameter effects. The presence of an output schema handles return details, so the description completes the picture.

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 sole parameter `materialize_templates` is explained precisely: passing False yields 'bare-bones directory layout only (no shipped state ledgers, sensors, actions, or playbooks)'. This compensates for the schema's 0% parameter coverage.

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 opens with a clear verb-resource pairing: 'Create `.keystone/harness/` and (by default) materialize the shipped template tree.' It distinguishes itself from sibling scaffolding tools by noting it is a prerequisite ('Call this once per project before scaffolding individual guides / sensors / actions / playbooks').

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?

Explicit when-to-use guidance is provided: 'Call this once per project before scaffolding...' It also explains when to opt out of the default behavior ('opt out only for advanced use cases'), giving clear decision criteria.

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