Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral context: the response structure (authenticated boolean, pending list, connect_url) and the two possible states. No contradictions.
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 sentences, each earning its place. First sentence states the core function, second sentence explains the two possible outcomes. No unnecessary words.
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, the description fully explains the return values and the two states. It is complete for a simple status check tool with no 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 tool has 0 parameters and schema coverage is 100%, so baseline is 4. The description adds value by explaining what the tool returns, which compensates for the lack of output schema.
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 returns connection status and URLs, with specific examples of output when all providers are connected vs when credentials are missing. This distinguishes it from sibling tools like 'authenticate' and 'marketplace'.
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 when to use (checking connection status or getting URLs for missing credentials) but does not explicitly state when not to use or name alternatives. It gives good context but lacks explicit exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The openfinance_* tools are cleanly separated by resource and action (accounts, transactions, bills, investments, loans, connections), and the list-versus-get patterns are distinguishable. The main weak spots are the broad 'marketplace' tool, which bundles many sub-actions, and mild overlap between list_accounts/get_account_balance and list_transactions/list_transactions_by_item.
The banking tools follow a consistent openfinance_<verb>_<noun> convention, with list_/get_ prefixes used predictably. A few deviations like 'provider_status' (missing a verb) and non-prefixed platform tools (authenticate, connect, marketplace, toolkit_info) keep it from being perfectly uniform.
25 tools is on the heavy side, but the Open Finance domain justifies a wide surface: balances, transactions, bills, investments, loans, connections, sync, and provider health each need their own entry points. The platform/meta tools add some bulk but are individually useful.
The Open Finance surface covers the full read lifecycle: discover/search connectors, connect via URLs, list and inspect connections, force sync, check provider/connection status, and read accounts, balances, transactions, credit card bills, investments, and loans. It also supports the one clearly expected write operation (transaction category correction), leaving no obvious dead ends in the core domain.