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

Annotations already declare readOnlyHint=true, but the description adds genuinely useful behavioral facts: results are not paged, and there is a vendor rate limit of 60 req/min and 1000 req/24h, with each call counting as one request. That is exactly the kind of operational context annotations cannot express.

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?

Three compact sentences in a telegraphed style: returned fields first, then endpoint/pagination, then rate limits. Every sentence carries information; the only minor cost is the terse, fragmentary phrasing.

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?

With no output schema and no parameters, the description compensates by listing the returned fields and the pagination behavior, plus the rate-limit constraint an agent must respect. Nothing critical to correct invocation is missing, though the lack of sibling differentiation is a small residual gap.

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 takes zero parameters, so the baseline is 4. The description sensibly uses the space to explain the returned shape instead of inventing parameter guidance.

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?

Names the resource (the company's bank accounts) and enumerates the returned fields (name, ledger account, currency, IBAN, SWIFT), so an agent knows exactly what data comes back. It does not explicitly distinguish itself from similarly named siblings like smartaccounts_list_accounts or smartaccounts_list_cash_accounts, which is the only thing keeping it from a 5.

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?

Usage is implied by the list semantics and the '(settings/bankaccounts:get)' endpoint reference, and the 'Not paged' note tells the agent it can consume results in one shot. However, there is no explicit when-to-use statement or pointer to the sibling list tools it could be confused with.

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