kalshi_get_subaccount_balances

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool's safety profile is clear. The description adds the endpoint and the inclusion of the primary account, which is helpful context. However, it does not disclose the return structure or any other behavioral details, so it provides only marginal value beyond the annotations.

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 only two sentences, with the actual purpose in the second sentence and the endpoint in the third. The first sentence is somewhat redundant with the tool name, but overall the text is short and front-loaded, with no wasteful content.

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 parameterless GET endpoint, the description sufficiently conveys what it does and its scope. The lack of an output schema means the description does not need to explain return values, and the tool's straightforward nature makes this adequate. It could mention what balance fields are returned, but that is a minor 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 input schema has zero parameters, so a baseline of 4 is appropriate. The description's mention of 'all subaccounts including the primary account' is a semantic qualifier rather than a parameter, and no parameter-level detail is needed.

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 opens with 'Get All Subaccount Balances' – a clear verb+resource pairing – and further specifies 'all subaccounts including the primary account,' which distinguishes it from sibling tools like kalshi_get_balance. It also names the exact endpoint, making the action unambiguous.

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 states the tool's scope ('all subaccounts including the primary account'), giving clear context for when to use it over account-specific balance tools. It does not explicitly name alternatives or exclusions, but the scope is informative enough for an agent to select it appropriately.

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