kalshi_balance

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

With no annotations, the description carries the burden of behavioral disclosure. It does state a key requirement ('needs the operator's API key'), which is useful context. However, it does not describe the nature of the operation (read-only), potential rate limits, or other behaviors. Since an output schema exists, return format is not needed, but the description could add more about authentication or expected behavior.

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?

A single, direct sentence that is front-loaded with the core purpose and the key prerequisite. No wasted words, appropriate for the simplicity of the tool.

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 parameterless balance-check tool with an output schema present, the description is largely sufficient. It conveys the purpose and the API key requirement. Minor omissions, such as clarifying this is a read-only operation, are not critical given the tool's simplicity.

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 nothing to explain. The baseline for 0 parameters is 4, and the description adds no conflict or extra meaning that detracts from this.

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 resource ('Kalshi account balance') and implies retrieval. It is specific and easily distinguished from sibling tools, none of which directly reference account balance.

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 guidance is given on when to use this tool versus alternatives, nor are any alternatives mentioned. Since the tool is simple and has no parameters, some guidance on prerequisites or typical use cases would be helpful but is absent.

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