sb_list_sub_accounts

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

No annotations are provided, so the description carries full burden. It only states it 'List sub-accounts', implying a read operation, but does not disclose any behavioral traits such as pagination behavior, data freshness, or that it is safe (non-destructive).

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, concise sentence (5 words) with no wasted words. However, it is too minimal to provide adequate guidance, earning a middle score.

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 tool has 3 parameters including pagination and an output schema exists, the description is incomplete. It does not mention that the tool returns a list of sub-accounts, how pagination works, or how to obtain all sub-accounts.

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%, so the description should compensate by explaining parameters. It does not mention that storage_box_id identifies the storage box, or that page and per_page control pagination. Parameter names are somewhat intuitive, but the description adds no semantic value beyond the schema.

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 'List sub-accounts of a Storage Box' uses a specific verb (List) and resource (sub-accounts of a Storage Box), clearly distinguishing it from sibling tools like sb_list_storage_boxes (lists storage boxes) and sb_get_sub_account (gets a single sub-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 the tool should be used to list sub-accounts of a specific storage box, but does not provide explicit guidance on when not to use it or alternatives (e.g., sb_get_sub_account for a single sub-account). No mention of pagination or result handling.

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