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

With no annotations, the description carries the full burden and does disclose what an agent would otherwise have to guess: read-only semantics, the 92-day cap on ranges, that empty days are omitted from results, and that each day comes with text plus a one-line summary. It stops short of stating permission requirements or error behavior for malformed ranges.

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?

One sentence, no filler, and the most important facts (personal scope, read, two modes) come first. The deeply nested parentheses around the range parameters make it slightly dense to parse but nothing is wasted.

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 3-param, no-output-schema read tool this covers nearly everything: defaults, format, range limit, return shape, and empty-day handling. The remaining gap is precedence when multiple date parameters are combined, which an agent would have to discover by experiment.

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, and it does: 'date' is documented with a default of today, 'from'/'to' are documented with YYYY-MM-DD format and a 92-day maximum. It does not say what happens if 'date' and 'from'/'to' are supplied together, which leaves one real ambiguity for a 3-param tool.

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?

Opens with a specific verb and resource ('Read the user's journal') and immediately scopes it as 'always personal', which separates it from workspace-scoped siblings and from the writing counterpart journal_write. It never names a sibling explicitly, so the differentiation is implicit rather than spelled out.

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 two modes (single day vs. date range) imply when each applies, and 'default today' gives a sane fallback, but the description never states when to prefer a range over a single day or when to use journal_write instead of reading. Usage is inferable but not guided.

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