calculate_kite_order_charges

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

Description is too brief to disclose behavioral traits such as whether it requires an active broker session, whether it places orders, or what the breakdown includes. With no annotations, the description carries the full burden but does not address any side effects or prerequisites.

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?

Single concise sentence, front-loaded with the verb and resource; no unnecessary words.

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?

The tool accepts a complex nested orders array and has no output schema, but the description offers no information about return format, per-order vs aggregate breakdown, or any limitations. This is insufficient for an agent to anticipate the tool's behavior.

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 has 100% coverage, so the description doesn't need to add parameter details. The description adds no extra meaning beyond the schema's existing property descriptions, giving a baseline score of 3.

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 a specific verb ('Get') and resource ('detailed charges breakdown for Kite orders'), clearly distinguishing from sibling margin calculation tools like calculate_kite_order_margins. The purpose is unambiguous.

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 on when to use this tool versus alternatives such as calculate_kite_order_margins or calculate_kite_basket_margins. The description only states its function without exclusions or alternative recommendations.

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