update_frontmatter

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

No annotations present; description discloses that note body is left untouched. However, it does not mention error handling, permission requirements, or atomicity.

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?

Single clear sentence with immediate verb and resource. No extraneous text. Key actions (merge set, delete remove) are front-loaded.

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?

Tool has only 3 parameters and no output schema. Description covers the core behavior (updating frontmatter without touching body). Minor gaps: no mention of return value or error cases.

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 'merged into existing frontmatter' for set and 'Keys to delete' for remove, providing context beyond schema property descriptions.

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?

Description uses specific verb 'Update' and resource 'YAML frontmatter', clearly distinguishing from sibling tools that modify note body or create/read notes.

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?

No explicit when-to-use or when-not-to-use guidance. Sibling tools are listed but not referenced. Implicitly, it's for frontmatter modifications only.

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