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

Beyond the readOnlyHint annotation, the description provides substantial behavioral detail: default status 'all' shows open+closed, void is hidden unless explicitly asked, open trades include live unrealized PnL and stop-level warnings, closed trades show resolved outcomes, and a stats block gives personal calibration. These details go far beyond the annotation and help the agent predict tool behavior.

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 front-loaded with the main action and logically organized. It is somewhat long but mostly information-dense; however, the '[JOURNAL]' tag and trailing 'Pro.' are unnecessary and slightly detract from conciseness. Overall, it earns its length with useful details.

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 adequately explains what the tool returns: open trade details (PnL, R, stop warning), closed trade details (ret %, R, MAE/MFE), and a stats block. It also covers parameter effects and default behavior, making it complete for a read-only journal tool with simple parameters.

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?

The input schema has no descriptions and 0% coverage, so the description fully carries the burden. It explains the 'status' values (open, closed, void, all) including the default behavior and hidden void, and explains 'limit' as history length with default 20. This is complete for the two parameters.

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 tool's purpose with a specific verb and resource: 'Read your private trade journal.' It distinguishes itself from sibling tools by focusing on the journal and explaining its contents (open/closed trades, stats). This makes it unambiguous among many get_* tools.

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 description implies clear usage context: use this to read your journal, with status and limit controlling scope. It doesn't explicitly mention when to avoid this tool or alternatives, but the context is sufficiently clear given the unique journal focus. A brief 'use for personal trade history' would strengthen it, but the default behavior and statuses are well explained.

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