calculate_kite_basket_margins

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the calculation intent, omitting any mention of read-only nature, authentication requirements, or potential error conditions. This leaves the agent without information about side effects or permissions.

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 a single, front-loaded sentence with no redundancy. Every word contributes to the core purpose, making it highly concise and well-structured.

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?

Despite a clear schema, the description omits crucial context such as what the output looks like (no output schema exists), when to choose this over the similar calculate_kite_order_margins, and any constraints on the 'orders' array for spread orders. The tool's complexity and the presence of closely related siblings demand more explanatory content.

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 provides 100% description coverage for all four parameters, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema already documents, such as the need for 'broker' to be 'kite' or the optional nature of 'mode'.

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 calculates basket margins specifically for spread orders on Kite, distinguishing it from sibling tools like calculate_kite_order_margins which handle single orders. The verb 'Calculate' is specific and the resource 'basket margins' is well-defined.

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 on when to use this tool versus alternatives such as calculate_kite_order_margins or calculate_order_margin. The description implies a use case for basket/spread orders but does not explicitly state the distinction or provide exclusions.

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