memshelf_init

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds value by confirming 'Idempotent — never overwrites existing files' and describing storage options (plain, git-local, git-remote). This provides behavioral context beyond the annotations.

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 two sentences: the first specifies what gets created, the second covers storage and idempotency. Every sentence adds value, no fluff. Front-loaded with the core 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 that an output schema exists and the tool has moderate complexity (4 parameters, one enum), the description covers the essentials: shelf structure, storage options, and idempotency. It could mention prerequisites like git availability but is otherwise complete.

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 reportedly 0%, so the description must compensate. It mentions storage types and idempotency but does not detail parameters like 'name', 'remote', or 'shelf_path'. Some context is provided but not enough to fully clarify parameter meaning.

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?

Clearly states the tool creates or tops up a memory shelf with specific contents (docshelf layout, INDEX preamble, etc.), distinguishing it from sibling tools like memshelf_shelve or memshelf_recall. The title annotation 'Bootstrap a memory shelf' reinforces this.

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 provides clear context on what the tool does (initialize a shelf) but does not explicitly state when to use it versus alternatives like memshelf_import. However, the purpose is self-explanatory enough that an agent would infer usage.

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