Synapse

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

The description adds valuable behavioral context beyond annotations: it specifies that it's 'Safe to run on an existing vault — won't overwrite existing files,' which clarifies idempotent behavior in practice. Annotations already indicate idempotentHint=true and non-destructive, but the description enhances this with real-world implications. No contradictions with 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 front-loaded with the core purpose, followed by key behavioral details and usage guidelines. Every sentence adds value: the first explains what it does, the second clarifies safety, and the third provides critical usage context. No wasted words, and it's structured for quick comprehension.

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 tool with one parameter (fully covered by schema), rich annotations, and no output schema, the description is nearly complete. It covers purpose, behavior, and usage context effectively. A minor gap is lack of detail on output (e.g., what files are created), but given the annotations and simplicity, this is acceptable.

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 input schema has 100% description coverage, with the 'topic' parameter fully documented in the schema. The description does not add any additional parameter semantics beyond what the schema provides, such as examples or constraints. Baseline score of 3 is appropriate since the schema carries the full burden.

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 the specific action ('Initialize a structured knowledge base') and the resources involved ('creates the folder structure, generates CLAUDE.md with the schema, and creates the initial index and log files'). It explicitly distinguishes from sibling 'synapse_setup' by specifying 'For new vaults only' versus existing vaults, providing clear differentiation.

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 explicit guidance on when to use this tool ('For new vaults only') and when not to ('If you have an existing vault, use `synapse_setup` instead'). It names the alternative tool and explains the context for each, making it clear when to choose this over siblings.

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