Create note from template

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

Annotations (readOnlyHint=false, destructiveHint=false) are present, so the bar is lower. The description adds value by explaining variable substitution, but it does not disclose the side effect of overwriting an existing note when overwrite=true, which contradicts destructiveHint=false. However, this contradiction is between annotation and parameter, not the description. The description itself is accurate but incomplete regarding error handling.

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 core functionality. Every word is meaningful with no redundancy.

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 tool has 5 parameters, nested objects, and no output schema, the description is too brief. It omits critical context such as what happens if the template does not exist, whether errors are returned, or what the outcome of a successful call is.

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 baseline is 3. The description adds meaning beyond the schema by explaining that {{title}}, {{date}}, {{time}} are substituted and that custom variables are supported. This provides useful context about how parameters are used.

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 the action (Create a note from a template) and the specific behavior of substituting {{title}}, {{date}}, {{time}} and custom variables. This distinguishes it from sibling tools like create_note, which creates a blank 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?

No guidance is provided on when to use this tool versus alternatives (e.g., create_note for blank notes). There is no mention of prerequisites, such as the template needing to exist or be correctly specified.

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