List journal accounts

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

The annotations already declare a safe read-only open-world operation, and the description adds important behavioral context: OAuth sign-in requirement, empty-list semantics, and the downstream constraint that other tools reject unknown account ids. It also discloses the returned account metadata without needing an output schema.

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 purpose and then usage guidance, and every clause adds useful information. It is somewhat dense because it lists many returned fields in one long sentence, but that detail is justified without an output schema.

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?

Given no output schema and no input parameters, the description fully covers what the tool returns, when to call it, authentication requirements, and empty-state behavior. An agent has everything needed to invoke it 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?

The tool has zero input parameters, so there are no parameter semantics to describe. The baseline for a no-parameter tool is 4, and the description does not need to compensate for missing schema coverage.

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 and resource: listing the signed-in user's trade-journal accounts. It also enumerates the returned fields and distinguishes itself from siblings by saying other journal tools' `accounts` filters depend on these ids.

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 explicitly says to call this first, explains why other journal tools reject unknown account ids, and notes that journal_add_trade requires a `manual` or `import` account. It also tells the agent what an empty list means and what authentication is required.

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