append_to_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 behavioral burden. It discloses creation of the note and parent directories, the configurable path format, and the return value type. It omits minor details such as timezone handling and how subsection headings are matched/created, but the core side effects are transparent.

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 well-structured and front-loaded: it opens with the core purpose, then adds behavioral context, an exclusion, and a brief args/returns section. Every sentence serves a purpose and there is no redundant filler.

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 only 2 parameters, no annotations, and an output schema, the description covers the essential context: what it appends, where, creation side effects, path configuration, return value, and when not to use it. Minor gaps like timezone and exact subsection formatting prevent a perfect score.

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 description coverage is 0%, so the description must compensate. It provides one-line meanings for both parameters ('Content to append' and 'Optional heading title to append under'). However, it does not explain formatting conventions, newline handling, or how an existing subsection is located, leaving meaningful ambiguity.

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 states a specific verb ('Append'), a clear resource ('today's daily note'), and a qualifier ('under an optional subsection'). It also distinguishes itself from log_to_daily_note by noting that sibling handles timestamped log entries, making the tool's purpose unmistakable among the many siblings.

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 routes timestamped log entries to log_to_daily_note, giving a clear when-not and an alternative. It also implicitly distinguishes from append_to_note by specifying 'today's daily note', though it does not name that sibling or other daily-note-related tools like create_daily_note.

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