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

The description discloses meaningful behavior by warning to preserve ^task markers and read before replacing. However, the annotations declare destructiveHint=false while the description's replace mode and preservation warning indicate destructive data-loss risk, which is an annotation contradiction that leaves an agent with conflicting signals.

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 with no filler; the core action is front-loaded and the second sentence adds an important behavioral caveat. Every word carries weight.

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?

For a mutation tool with no output schema and sparse annotations, the description is minimally viable but incomplete: it does not specify the mode default, date format, response behavior, or how to preserve task markers beyond a short instruction. An agent can invoke it correctly for basic cases but may guess on edge cases.

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?

With 0% schema description coverage, the description provides some parameter meaning: it explains the mode choices (append/replace), implies content is journal text, and adds the ^task marker requirement. Still, date semantics and content format are not explained, so it only partially compensates for the schema gap.

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 uses a specific verb phrase 'Append or replace a journal,' naming the exact action and resource. It also signals that this is the write counterpart to tools like get_journal, distinguishing it from the read and goal/task 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?

It clearly implies use when the agent needs to create or modify a journal by appending or replacing content. It lacks an explicit exclusion or pointer to get_journal as the alternative, though the instruction to 'Read before replacing' strongly suggests the prerequisite read path.

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