memorybank_initialize

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

With no annotations, description discloses it does not use AI, creates static templates, and requires absolute path. Could mention idempotency or overwrite behavior, but current coverage is good.

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?

Well-structured with bullet list of files and warnings. Slightly verbose but informative. Every sentence adds value.

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?

Covers purpose, usage, parameter constraints, and sibling differentiation. Lacks return value description but is sufficient for an initialization tool without output schema.

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 coverage is 100%. Description adds the absolute path requirement example, and clarifies projectId is mandatory. Adds value beyond schema for projectPath.

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 states it initializes Memory Bank for a new project by creating directory structure and 7 markdown documents with templates. It lists the exact files and distinguishes from sibling memorybank_generate_project_docs.

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?

Explicitly says when to use (new project initialization) and when not to (use memorybank_generate_project_docs for detailed docs). Includes requirement for absolute path.

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