list_bank_accounts

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

The description adds no behavioral context beyond what annotations already provide. Annotations include readOnlyHint=true and destructiveHint=false, which imply safety, but the description does not elaborate on the nature of the listing (e.g., pagination, sorting, or the open world hint that the list may be incomplete).

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 extremely concise (one phrase), which is appropriate for a parameterless list tool. However, it lacks any structural elements that could improve readability or quick comprehension.

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 the lack of output schema, the description should clarify what the list returns (e.g., summary information or full details) and mention the openWorldHint implications. It fails to provide this context, leaving the agent uncertain about the tool's output.

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 parameters, so schema coverage is 100%. The description offers no additional semantic information, meeting the baseline of 3 per the scoring guidelines.

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 'Bankszámlák listázása' clearly translates to 'Listing bank accounts', which accurately reflects the tool's purpose. It specifies the resource (bank accounts) and action (list), but does not differentiate from sibling list tools like list_documents or list_partners, though the resource distinction is clear.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives like get_bank_account for a specific account, or any context about appropriate use cases.

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