create_daily_note

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

No annotations are provided, so the description carries the full burden. It transparently discloses template-based creation, full structure, and idempotent behavior: if the note already exists, it returns a message without overwriting. It does not mention failure modes like a missing template, 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?

The main purpose is front-loaded in the first sentence. The following sentences add non-redundant specifics about structure, idempotency, parameters, and return value. There is no filler 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?

With only two optional parameters, a provided output schema, and no annotations, the description is complete enough for an agent to invoke the tool correctly. It covers parameter formats, defaults, behavior when the note exists, and what is returned.

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?

The input schema has 0% description coverage and only states types and defaults, so the description must compensate. It fully does: it explains date is in YYYY-MM-DD format, defaults to today, and extra_vars is an optional dictionary of template variables.

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 opens with a specific verb and resource: 'Create today's daily note from the configured template.' It also clarifies the note is fully structured with standard frontmatter fields and sections, which distinguishes it from sibling tools like append_to_daily_note, create_weekly_note, and log_to_daily_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 intended use is clear: create the daily note from a template. The no-overwrite clause subtly implies this is not for adding content to an existing note, but it does not explicitly name alternatives like append_to_daily_note or state when to choose them.

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