Create Daily Note

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

The description discloses key behaviors: creation, failure on duplicate, optional template with date substitution. Annotations (readOnlyHint false) align with this. It could add more about default date behavior or folder existence, but is sufficient.

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 core functionality, no unnecessary words. Every sentence adds value.

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?

For a tool with 3 optional parameters and no output schema, the description fully explains creation behavior, template feature, and failure condition. Annotations provide no contradictions.

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 clear descriptions for all 3 parameters. The tool description adds minimal beyond the schema (e.g., 'fails if exists'), so baseline 3 is appropriate.

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 tool creates a daily note for a specific date in the configured folder with proper filename format. It distinguishes from siblings like 'create_note' and 'get_daily_note' by specifying daily-note context.

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 implies usage for creating daily notes and warns that it fails if already exists. However, it does not explicitly mention alternatives like 'create_note' for non-daily notes, though the sibling list provides context.

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