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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description's idempotency sentence mostly restates structured data; the added value is only the observable detail that an existing name 'succeeds without creating duplicates.' It says nothing about permissions, error behavior, or whether parent segments of a path are auto-created.

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 short sentences, each doing distinct work: purpose, usage, idempotency. The core purpose is front-loaded with zero 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?

An output schema exists and the vault_id parameter is fully specified in the schema, so the description need not cover returns or vault targeting. The one material gap is whether a nested path like 'Projects/Active' implicitly creates 'Projects', which matters for a path-based folder tool.

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%, so both parameters are already documented, including the vault_id multi-vault rule, which the description does not touch. The description's phrase 'existing folder name' is slightly looser than the schema's 'Folder path, e.g. "Projects/Active"', adding no real semantics beyond the schema.

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?

States a specific verb+resource ('Create an explicit empty folder') and scopes it to 'the personal knowledge base.' It implicitly distinguishes itself from create_note and suggest_folder via 'explicit empty folder,' but never names a sibling, so differentiation is left to inference.

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?

'Use to scaffold folder structure before placing notes' gives a concrete when-to-use context. It does not, however, mention alternatives (e.g. suggest_folder for discovering names, list_folder for checking existence) or any when-not-to-use condition.

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