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 explains that it appends timestamped lines or reads if text is empty, and that it keeps a single entry per day. However, it omits details like timezone handling, creation behavior, and any potential limits, making it adequate but not thorough.

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 concise with four sentences: core function, sibling comparison, usage pattern, and parameter explanation. Every sentence adds value, with no wasted words and clear structure.

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's simplicity (one optional parameter, no annotations, and an output schema likely covering return values), the description is near-complete. It covers usage, parameter semantics, and behavioral pattern. A minor gap is the lack of explicit mention that it operates on the current day, but this is implied by 'today's daily note'.

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 schema provides no description for the 'text' parameter (0% coverage). The description adds clear meaning: a line to append, and leaving it empty triggers a read. This fully compensates for the schema gap and adds precise usage semantics.

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 (append or read) and resource (today's daily note). It distinguishes from the sibling tool add_journal_entry by explaining the single-entry-per-day pattern, making the purpose specific and unambiguous.

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 explicitly contrasts daily_note with add_journal_entry, indicating when to use this tool (for fast, low-friction capture in a daily note). It provides clear context but could be more explicit about when not to use it, though the comparison is effective.

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