Get one journal day

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

Annotations already cover read-only and open-world nature, but the description adds real behavioral detail beyond them: stats is null when nothing traded, how 'trades' is defined (closed that day OR opened that day and still open), and that OAuth sign-in is required. These edge cases and the auth requirement meaningfully improve invoke correctness.

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?

Front-loaded with the return payload, then the date key, then usage, then auth requirement — each clause earns its place with no padding.

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?

With no output schema, the description correctly enumerates the return shape (stats, trade summaries, notes with ids) and discloses the auth prerequisite. It stops just short of noting the accounts scoping or any pagination/limit behavior, but is otherwise complete for invoking the tool.

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 both `date` and `accounts` are already fully documented in the schema. The description restates the date format but adds no syntax or semantics beyond it, and omits the accounts scoping entirely, leaving the schema to carry the load — the baseline 3.

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 states exactly what the tool returns for a specific resource (a single trading day): stats, trade summaries, and notes with ids. The single-day scope inherently distinguishes it from aggregate siblings like journal_overview or journal_calendar, so an agent can route correctly without opening the schema.

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 gives concrete when-to-use guidance ('how did Tuesday go') and a downstream workflow ('to find note ids for journal_update_note'), which is genuinely useful routing. It lacks an explicit when-not or a named alternative tool, so it lands at 4 rather than 5.

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