get_margin_for_orders

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

No annotations are provided, so the description carries the burden. It discloses the Groww-only restriction, which is a behavioral constraint, but does not mention authentication prerequisites, potential side effects, or what happens if the Groww session is invalid. For a calculation tool, this is moderate but incomplete transparency.

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 one sentence, front-loaded with the verb and resource, and contains zero waste. It is minimal but effective.

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 tool with three params, rich schema descriptions, and no output schema, the description adequately conveys core purpose and broker restriction. It lacks some context like whether an active Groww session is required, but the schema's broker parameter description reinforces the Groww-only constraint, making the tool usable.

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 description coverage is 100%, so the schema already documents all parameters thoroughly (orders array, broker enum, segment enum). The description adds no additional parameter context beyond what the schema provides, which is acceptable per the baseline.

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 verb (Calculate), resource (required margin), and scope (multiple orders, Groww only). It distinguishes from sibling margin tools like 'calculate_order_margin' (singular) and 'calculate_kite_order_margins' (Kite-specific) by explicitly specifying 'multiple orders' and 'Groww only'.

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 'Groww only' qualifier provides clear context for when to use this tool — specifically for Groww broker margin calculations on multiple orders. However, it does not explicitly mention alternatives for single-order or other brokers, so it lacks when-not guidance.

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