Journal

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

The readOnlyHint annotation already covers the safety profile. The description adds that it returns 'all transactions in chronological/posting order' and defaults to JSON, which is useful but minimal. It does not explain pagination, filtering options, or output structure beyond the raw journal.

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 short sentences, front-loaded with the core action and scope. No redundant fluff; every word serves a purpose.

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 read-only report tool with no required params and full schema coverage, the description is adequate. It conveys the fundamental behavior and default format. It lacks explicit mention of output shape, but that is less critical given the simplicity and read-only nature.

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 descriptions cover all 4 parameters, so the description need not add much. The description does mention default JSON format, which echoes the schema, but does not provide additional meaning beyond schema fields.

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 a specific verb ('Return') and resource ('journal'), and clarifies that it includes all transactions in chronological/posting order. This clearly distinguishes it from sibling tools that focus on balances, accounts, or specific table views.

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 context implies use for retrieving the full transaction journal of a document, but it does not explicitly mention alternatives or when not to use it. Sibling tool names suggest there are other report tools, but no exclusions or comparisons are provided.

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