ofw_list_journal_entries

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

The description goes well beyond the readOnlyHint annotation by detailing the paging contract: offset paging with 1-based start/max, response shape with hasMore and nextStart before records, the null meaning of nextStart, and the warning never to state an entry count or absence from a single page. This is substantial non-obvious behavioral context.

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 three tightly packed sentences with no filler. It front-loads the core purpose, then communicates the paging behavior and the critical agent-facing caveat, so every sentence earns its place.

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 simple read-only list tool with two optional parameters, the description is complete: it identifies the resource, the paging mechanism, the response paging fields, and the key interpretation pitfall. The schema covers parameter defaults and continuation, and the annotation covers safety, so an agent can invoke and interpret the tool correctly.

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 baseline is 3. The description mentions 'start/max' and '1-based' but the input schema already documents defaults, ranges, and how to continue with nextStart. The additional paging-state information is response behavior rather than new parameter-level meaning.

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 opens with a specific verb and resource: 'List OurFamilyWizard journal entries.' This clearly distinguishes it from sibling tools that list events, messages, expenses, or drafts, and it is not a tautology.

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 resource-scoped purpose makes the selection context clear, and sibling tools target different resources, so an agent can choose this tool without much ambiguity. However, it does not explicitly name alternative tools or state when not to use this tool, so it falls short of a 5.

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