get_margins

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

No annotations are provided, so the description carries the full burden. It states the core behavior (getting margins) and the session context, but it does not disclose potential failure modes (e.g., no active broker), return format, or whether the operation is read-only beyond the verb 'Get'. The description adds some session context but is not rich in behavioral detail.

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 sentence of 13 words, front-loaded with the verb 'Get' and the primary object 'account margins'. There is no redundant or extraneous wording, making it highly concise and easy to parse.

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?

Given the tool's simplicity (2 optional params, no output schema, no annotations), the description covers the primary purpose but omits useful context such as what margin figures are returned (e.g., available vs. used margin) and prerequisites like requiring an authenticated broker. It is adequate for a simple getter but leaves gaps that could affect correct usage.

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 is 100%: the broker parameter already explains it is optional and uses the active broker if not specified, and the segment parameter is clearly scoped to Kite. The description only reinforces the 'active or specific broker' concept without adding new semantic meaning or elaborating on parameter interactions, so it provides marginal value beyond 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 uses the specific verb 'Get' with resource 'account margins' and scoping 'from active or specific broker in your session.' This clearly distinguishes it from sibling tools like calculate_order_margin or get_margin_for_orders, which focus on order-specific margin calculations rather than account-level margins.

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 use when account-level margins are needed, but it does not explicitly state when not to use this tool or mention alternatives such as calculate_order_margin for order-level calculations. It also lacks guidance on prerequisites like requiring an active authenticated broker session, leaving usage context partially implicit.

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