List Accounts

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's role in behavioral disclosure is minimal. It adds the scope qualifier 'accessible to the authenticated user' but does not describe output format, pagination, or other behavioral traits. The description is not contradictory and adds slight context, so a moderate score is appropriate.

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 sentence with no redundant wording. It front-loads the action and resource, and the scope qualifier is concise. No unnecessary detail.

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 an output schema, the description could provide more detail about what an 'account' entails (e.g., fields like ID, name). However, the tool is simple, and the description covers the core behavior. The scope qualifier adds some context, but it does not specify return structure or any additional behavioral nuances, leaving some gaps.

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?

There are zero parameters, so the input schema is empty and the description does not need to compensate. The description adds no parameter-specific information because none exist; a baseline of 4 is justified.

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 states the action (list), resource (accounts), and scope (accessible to the authenticated user). It distinguishes itself from sibling tools like list_sub_accounts (which lists sub-accounts) and get_account (which fetches a single account).

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?

The description implies when to use the tool (when you need all accounts for the user) but does not explicitly contrast it with alternatives like list_sub_accounts or get_account. No when-not-to-use guidance is provided, leaving the agent to infer from sibling names.

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