Get all accounts

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

readOnlyHint=true already tells the agent this is a safe read, so the description doesn't need to restate safety. It does add that results are scoped to the logged-in holder and that one holder may have several accounts, which is useful context. It says nothing about pagination or result volume, and with an output schema present, return-format disclosure is not required.

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 short sentences, with the core purpose front-loaded and the usage hint immediately after. The multi-account example sentence is arguably illustrative padding, but it does clarify the expected result shape and is not wasteful.

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 zero parameters, an output schema to describe returns, and read-only annotations, the description covers what an agent needs to select and call this tool. A brief note on pagination or ordering would close the remaining 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 per the rubric the baseline is 4. There are no parameter semantics to clarify, and the description correctly does not invent any.

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 states a specific verb+resource: 'Get all accounts associated with the logged in account holder.' The scope (all accounts for the authenticated holder) is clear. It does not, however, explicitly contrast itself with sibling tools such as account_holder_get or account_identifiers_get, so an agent must infer the difference.

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?

'This is typically the first call to make to get account information' gives clear sequencing context for when to reach for this tool. It stops short of naming alternatives or stating when not to use it, but the entry-point guidance is genuinely useful.

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