list_transaction_accounts

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

With no annotations provided, the description must bear the full weight of behavioral disclosure, but it only says 'List' and 'for the authenticated user.' It doesn't mention pagination, ordering, response format, or any authentication nuances beyond the user scope, so the agent is left without important 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 a single, short sentence that immediately states the core action and resource. It contains no filler words or redundant information, achieving excellent conciseness and clear front-loading of the tool's 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?

Given that the tool has no parameters, no output schema, and no annotations, the description provides the essential information for an agent to know what it returns (a list of transaction accounts) and for whom (the authenticated user). It lacks explicit return format or pagination details, but for a simple, parameterless list tool, this is sufficiently complete.

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?

This tool has zero parameters and the schema coverage is 100%, so there are no parameter details to document. The description adds no parameter-specific meaning beyond the empty schema, but this is appropriate and earns the baseline score of 4 for a no-parameter tool.

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 action ('List'), resource ('transaction accounts'), and scope ('for the authenticated user'), making it unambiguous what the tool does. It also distinguishes itself from sibling tools like list_institution_accounts by the 'transaction' qualifier, so an agent can immediately recognize its purpose.

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 gives no guidance on when to use this tool versus alternatives such as list_accounts or list_institution_accounts. It only describes the action, leaving the agent without explicit context for choosing this over related tools.

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