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

Annotations already convey read-only, idempotent, non-destructive behavior. The description adds useful scope (accounts owned by the user plus partner-shared ones) and says the balance is current, but does not discuss response volume, auth, or rate limits; given the strong annotations, this is adequate but not rich.

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 16-word sentence with no filler. The topic 'Accounts' is front-loaded and every clause adds relevant information about returned attributes and access scope.

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 simple no-parameter read-only list with rich annotations, an output schema, and no nested objects, the description covers the returned fields and access scope well. It does not explicitly state 'returns all accounts' or mention sorting, but nothing required to invoke the tool successfully appears missing.

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 zero parameters, so there is no parameter-level meaning for the description to add; the baseline for 0-parameter tools is 4. The description appropriately clarifies output scope instead.

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 identifies the resource (accounts) and enumerates the returned attributes, including partner-shared accounts, which distinguishes it from sibling tools like list_holdings and list_categories. However, the description itself lacks an explicit verb such as 'list' or 'retrieve', relying on the title for the action.

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 when-to-use guidance or comparison with alternative tools is provided. The only indication of intended use comes implicitly from the name/title, with no exclusions or prerequisites stated.

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