Apply Template

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

The description details the variable substitution behavior, FORMAT tokens, and that Templater syntax is left literal. This goes beyond the annotations (destructiveHint=true) to clarify the tool's exact behavior, including edge cases.

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 two sentences, front-loaded with the primary action, followed by necessary details. Every sentence adds value with no redundancy or verbosity.

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 no output schema, the description explains the creation and substitution behavior well, but could optionally mention the return value or error handling beyond the 'fails' condition. However, it is sufficiently complete for the tool's complexity.

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% and the description adds significant meaning by explaining the variable substitution details, FORMAT token syntax, and the overwrite behavior. This helps the agent understand parameter usage 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?

The description clearly states it creates a new note from a template note, with specific variable substitution. This distinguishes it from 'create_note', which creates a blank note, making the purpose unambiguous and differentiated.

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 explains the failure condition when the target exists and the need for overwrite, but does not explicitly state when to use this tool over alternatives like 'create_note' or other sibling tools. Usage context is implied but not fully articulated.

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