daily_note

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

Discloses that it appends timestamped lines and keeps a single entry per day. With no annotations, it carries the full burden and does so adequately. Could be improved by noting the return format, but output schema may cover that.

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 plus args, front-loaded with purpose, no fluff. Every sentence earns its place.

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?

Complete for a simple append/read tool with one parameter and output schema present. Covers behavior, usage, and parameter semantics.

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?

Adds substantial meaning beyond the schema: 'text' is the line to append; leaving it empty reads the note. This compensates for 0% schema description coverage.

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?

States exactly what the tool does: append to or read today's daily note. Distinguishes from sibling 'add_journal_entry' by explaining the rolling note vs. new row behavior.

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?

Explicitly contrasts with 'add_journal_entry' to clarify when to use this tool (for daily note capture) vs. creating new journal entries. Also explains that leaving text empty reads the note, indicating a dual read/append use case.

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