update_frontmatter

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

Annotations only include openWorldHint:false, so the description carries the behavioral burden. It discloses that the operation is a merge and that the note body is untouched, but it does not explain how conflicting properties are handled, whether frontmatter is created if missing, or any other side effects.

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 a single, concise sentence that front-loads the key action ('Merge') and the key constraint ('without replacing the note body'). Every word earns its place.

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 the simple three-parameter schema and the clear sibling context, this description is largely complete. It distinguishes the tool from other note operations, though it could add detail on behavior when frontmatter is absent or how existing properties are treated in the merge.

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?

With 0% schema description coverage, the description must add meaning to the parameters. It indicates that 'properties' are the YAML frontmatter properties to merge, but does not explicitly describe the object structure of 'properties' or clarify the roles of 'vault' and 'path' beyond their names.

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 uses the specific verb 'merge' and clearly identifies the resource as 'YAML frontmatter properties'. The explicit constraint 'without replacing the note body' distinguishes it from sibling tools like update_note, which would update the entire note.

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 usage for frontmatter-only modifications and the phrase 'without replacing the note body' offers a clear contrast with whole-note updates. It does not explicitly name alternative tools or state when not to use it, but the context is sufficient for an agent to infer the appropriate scenario.

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