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

The description discloses auto-creation when the note is missing and makes it clear this is a mutating append, supplementing the annotations (readOnlyHint=false, idempotentHint=false). It does not go into side effects like parent-folder handling, but for a simple append the key behavior is covered.

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 entire description is one sentence with no filler, front-loading the core operation and then the conditional creation. Every word contributes.

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 three-parameter mutating tool, the description plus schema plus annotations cover the main call semantics, and the output can be inferred from the output schema. Minor gaps remain around edge cases such as whether missing parent folders are created, but nothing essential to a normal 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 100%, so the description is not required to elaborate on parameters. It adds no additional meaning beyond the schema's descriptions of path, text, and vault_id, except the contextual create-if-missing behavior. Baseline 3 is appropriate.

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 names a precise verb ('append') and resource ('text to an existing note') and adds the create-if-missing behavior, making it distinguishable from siblings like write_note and create_note. It is not a tautology and clearly states the operation's scope.

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 implies the appropriate context—use when text should be added to a note and created if absent—but it never explicitly contrasts with sibling tools such as write_note (overwrite) or patch_note (targeted update). No exclusions or when-not-to-use guidance is provided.

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