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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful freshness context by saying balances are 'last read from the bank' and including when they were read, but it omits pagination behavior and filter semantics.

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 a single front-loaded sentence plus a short safety tag, with no wasted wording. The 'Read-only' phrase duplicates the annotations slightly, but overall it is efficient.

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?

For a list tool with a complex nested filter and pagination parameters at 0% schema description coverage, the description does not explain how to narrow or page results. Output schema covers the return shape and annotations cover safety, but input usage remains materially under-described.

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?

Schema description coverage is 0%, and the description says nothing about the filter object, its many nested fields, pageSize, or pageToken. It adds no meaning beyond the input schema and does not compensate for the undocumented 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?

States a specific verb ('List') and resource ('company's bank accounts'), and names the returned data fields: available balance, current balance, and last-read timestamp. It does not differentiate itself from close siblings such as account_get_list_account_details or account_get_account, so it falls short of 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?

Provides no guidance on when to use this tool instead of account_get_account or account_get_list_account_details, nor on when to use filters versus pagination. 'Read-only' is a safety property already covered by annotations, not usage guidance.

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