log_journal_entry

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

With no annotations, the description carries full burden. It adds useful context with 'atomic file writing & de-duplication protection,' but does not explain what happens on duplicate entries (e.g., ignored, error, updated), any permission requirements, or error behaviors. This leaves important behavioral 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?

Two compact sentences: first sentence states the core purpose, second adds key behavioral details. No wasted words; information is front-loaded and appropriately sized.

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?

The output schema exists, so return values need no explanation. However, the description lacks explicit usage guidance and does not clarify deduplication semantics or what happens to existing entries. It is minimally viable but has clear gaps for a write tool with no annotations.

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 100%, so the schema already fully documents all six parameters. The description adds minimal parameter-level meaning, only grouping them via 'trade, market thesis, or trading theorem.' This matches the baseline for high schema 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?

The description clearly states the action ('Logs') and the specific resources ('trade, market thesis, or trading theorem') into a defined destination ('local Trading Journal database'). It also distinguishes itself from sibling tools like get_journal_summary by indicating a write operation.

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?

Usage context is only implied: the tool is for recording journal entries, and siblings like get_journal_summary read them. However, there is no explicit statement of when to use this tool versus alternatives, nor any exclusions or prerequisites.

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