kalshi_get_subaccount_transfers

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds the endpoint call and pagination detail. However, it does not disclose auth requirements, rate limits, or transfer-specific behaviors beyond what annotations cover. No contradiction found.

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 with the tool name, but the first phrase 'Get Subaccount Transfers' is redundant with the tool name. Overall it is efficient and conveys key information in two sentences.

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 paginated list tool with read-only annotations and full schema coverage, the description is sufficient. It specifies the endpoint and the resource, making the tool's purpose and behavior clear despite lacking an output schema.

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 coverage for parameters is 100% with descriptions for limit and cursor already in the schema. The description only mentions 'paginated' without adding new semantic detail, matching the baseline for full schema coverage.

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 tool 'Gets a paginated list of all transfers between subaccounts for the authenticated user', specifying both the action and the resource. It distinguishes itself from sibling tools like kalshi_apply_subaccount_transfer by focusing on read-only retrieval of transfers.

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 usage for listing subaccount transfers but does not explicitly mention alternatives or when not to use it. It provides context about pagination and the authenticated user, but lacks exclusionary guidance relative to sibling tools.

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