kalshi_get_total_resting_order_value

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context: the FCM restriction, the rare applicability, and that the value is in cents. It does not describe return format, but for a simple read-only endpoint the coverage is adequate.

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 concise: three sentences each add value—purpose, audience/usage, and API path. No filler or repetition.

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 read-only endpoint with no parameters and no output schema, the description is fully sufficient. It includes the endpoint path, the restrictive audience, and the return units, making it complete for an agent to select and invoke.

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?

There are zero parameters, so schema coverage is 100% by definition. Per the baseline for 0 params, this scores 4. The description adds context about units (cents) and the audience, which enriches understanding of the operation.

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 the total value of resting orders in cents, with a specific verb and resource. It also provides the exact API endpoint, distinguishing it from sibling tools that cover other portfolio/order data.

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?

Explicitly states this endpoint is intended only for FCM members (rare) and advises that if uncertain, it probably does not apply. This gives clear when-to-use guidance and an exclusion, even without naming alternatives.

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