kalshi_get_deposits

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'Calls GET /portfolio/deposits,' which merely reinforces the read-only nature and provides no additional behavioral context such as pagination behavior, rate limits, or response format beyond what the schema offers.

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 short and front-loaded, but the first sentence 'Get Deposits Endpoint for getting the member's deposit history' is slightly redundant. The second sentence adds the concrete endpoint reference, which is valuable for invocation.

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?

As a read-only list endpoint, the description plus schema pagination details are sufficient for correct invocation. It doesn't explain the return structure, but the schema's cursor description implies a paginated response, and 'deposit history' conveys the general output.

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?

Both limit and cursor are fully described in the schema, covering 100% of parameters with explicit meanings and defaults. The description adds no parameter-specific details, so it relies entirely on 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 clearly states it retrieves the member's deposit history and names the exact endpoint (GET /portfolio/deposits). It is specific to deposits, distinguishing it from siblings like kalshi_get_withdrawals, though it doesn't explicitly reference that alternative.

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 provided about when to use this tool versus alternatives. It only restates the function without contextual exclusions or mention of related tools such as kalshi_get_withdrawals.

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