place_bracket_order

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

With no annotations provided, the description bears the full burden of explaining behavior. It only says 'order with both stop loss and target,' but does not disclose that price is mandatory, that this is a limit order, order lifecycle implications, or any broker-specific behaviors or risks.

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, well-structured sentence that gets to the point instantly. It is appropriately concise, though it sacrifices meaningful content for brevity.

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?

This is a complex trading tool with 10 parameters and 7 required fields, yet the description provides only a minimal summary. It does not explain how the parameters relate, what a bracket order entails beyond stop loss and target, or how to successfully invoke it. The absence of an output schema makes the description even more insufficient.

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 covers 100% of parameters with descriptions, so the baseline is 3. The description adds little beyond restating the stop loss and target aspects, which are already evident from the 'stoploss' and 'squareoff' parameter names.

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 states a specific verb ('Place') and resource ('Bracket Order'), and clarifies that it includes both stop loss and target. This distinguishes it from basic order tools, though there is also a 'place_groww_bracket_order' sibling, so it could be more explicit about why this one is different.

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 given regarding when to use this tool versus alternatives like cover orders, iceberg orders, or the Groww bracket order variant. There is no mention of prerequisites, constraints, or scenarios that favor this tool.

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