claude_init_persistence

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

With no annotations, the description carries the burden and it delivers: it discloses idempotency, the no-op behavior when files exist, directory creation, the exact files written, and the effect of force. This goes well beyond a simple 'init' label.

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 action statement is front-loaded, followed by a tight idempotency note and a compact optional-fields list. No sentence is filler.

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 low-complexity initialization tool with zero required parameters and an output schema, the description covers location, file names, idempotency, force behavior, and template seeding. Nothing essential for a correct call is missing.

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 0%, so the description must compensate. It names force and seed_templates and gives a functional meaning for each, although it leaves the null-vs-false distinction for seed_templates slightly implicit.

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?

Begins with a specific verb and resource: 'Initialize the persistence directory and seed the three markdown files' and even names AGENTS.md, PROJECTS.md, MEMORY.md. This clearly separates it from sibling persistence tools that read, append, update, or load.

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?

Provides clear usage context through the idempotency statement: re-running is a no-op unless force=true, and explains what force does. It does not explicitly compare against alternatives or state when not to use it, so it falls just short of full guidance.

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