create_note_from_template

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

Without annotations, the description discloses the placeholder substitution behavior and the syntax for custom date formats. It doesn't mention error handling (e.g., if template doesn't exist) or output details, but the core behavior is well-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?

Two sentences, front-loaded with the purpose, and every sentence provides useful information. No unnecessary words or repetition.

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?

The description covers the main functionality but lacks details about the return value (path of created note?), what happens if the template doesn't exist, or whether the note path must not already exist. With no output schema, these gaps reduce completeness.

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% with descriptions for both parameters. The description adds value by explaining the automatic placeholder substitution and the '{{date:FMT}}' syntax, which goes 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 'Create a new note from a template' with a specific verb and resource. It distinguishes from siblings like 'create_note' and 'update_note' by highlighting the template-based creation and the follow-up step for custom content.

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 provides guidance on when to use this tool (for template-based creation) and when to use 'update_note' for custom content. However, it doesn't explicitly mention alternatives like 'list_templates' for finding available templates.

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