fintable_list_accounts

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the exact output fields (account names, balances, latest transaction dates, provider/bank/account IDs) and confirms it returns a JSON list. This is additive context, though no edge cases like empty lists are mentioned.

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 two short paragraphs plus a return type line, with the primary action front-loaded. Every sentence adds value, and there is no redundant information.

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 parameters, a simple list operation, and existing annotations, the description fully covers what the tool does and returns. No missing information like pagination or limits is needed for this straightforward 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?

The input schema has no user-facing properties (only a required empty params object), so no parameter descriptions are needed. The description correctly omits parameter details, and the baseline of 4 applies for tools with zero 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 states 'List all bank accounts connected to Fintable with balances and latest transaction dates.' This is a specific verb+resource combination that clearly distinguishes it from sibling tools like fintable_list_transactions or fintable_list_categories.

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 says 'Use this to get an overview of all connected financial accounts,' which provides clear context for when to use it. It does not explicitly mention when not to use it or alternatives, but the scope is unambiguous given sibling tools.

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