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

The annotations only declare readOnly/idempotent/non-destructive behavior, so the description carries the burden of disclosing caveats. It does this extensively: connector-dependent credit balance semantics, balance_notice meaning, provider_incident unreliability, identity_notice deduplication rules, and bankData lag. It even warns against telling the user the card has nothing to pay when balance_notice is present. No contradiction with annotations exists.

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 long but front-loaded with the core return values and scoping behavior before diving into caveats. Each major block—brand naming, credit balance caveats, incident notices, identity notices, bulk support—earns its place for safe usage. It is dense rather than padded, though a slightly tighter structure would improve readability.

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 a domain with many edge cases, the description is remarkably complete: it names the output fields, explains how to aggregate across connections, warns about unreliable values, and routes users to the right sibling for standardized card bills. An agent can invoke this tool safely and interpret results correctly without additional context.

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?

With 0% schema description coverage, the description compensates well by explaining item, the omission-of-item behavior, and item_ids for bulk execution. The type enum is partially covered through the account type explanation. However, it does not explicitly document the singular item_id parameter or formally state that type filters the returned accounts, leaving a small semantic gap.

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 opens with a specific verb and resource: "Returns accounts for a bank connection" and enumerates exactly which fields and account types are returned. It also distinguishes this tool from the sibling openfinance_list_credit_card_bills by explaining that standardized bill amounts come from that tool, making the purpose unambiguous.

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 explicit when-to-use guidance: "OMIT item to list accounts across ALL linked banks" versus "Pass item to target a single bank." It also tells the agent to use openfinance_list_credit_card_bills for reliable bill amounts and openfinance_force_sync to reconcile stale values, which fully supports correct tool selection.

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