journal_append

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

With no annotations, the description discloses file creation and same-day file_id behavior, which is useful. However, it does not specify safety aspects (e.g., whether it's read-only or destructive), rate limits, or authentication requirements, leaving gaps.

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 extremely concise: two sentences covering purpose, creation behavior, and return value. Every sentence adds value with no redundant or filler content.

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 low complexity (2 params, no output schema, no nested objects), the description fully covers what an agent needs: what the tool does, what it returns, and the idempotency behavior within a day. No missing critical details.

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%, so the schema fully documents the parameters. The description adds minimal value beyond stating the purpose of appending text and optional project context; it does not provide format or constraints beyond the schema.

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 timestamped text entry), the target (today's daily journal file), and key behaviors (creates file if missing, same file_id for same day). It effectively distinguishes from sibling tools like journal_note or distill_journal.

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 appending to today's journal but provides no explicit guidance on when to use this tool versus alternatives (e.g., journal_note, journal_intent). No exclusion criteria or when-not-to-use context is given.

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