Estimate Max Purchase Quantity

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the tool is clearly a read-only estimation. The description adds value by confirming the action ('Estimate') and detailing the return structure (cash_max_qty, margin_max_qty). No contradictions with annotations.

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 two sentences that front-load the main purpose and return type. Every word serves a purpose; no redundancy or fluff.

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 description is adequate for a simple estimation tool with good annotations and a full input schema. It specifies the return structure precisely. It could be improved by mentioning error handling or behavior when price is omitted, but overall it is sufficiently complete.

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% coverage with clear descriptions for each parameter. The description reinforces the parameter context by listing them and mentioning the optional price. It also explains the return 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 clearly states the verb 'Estimate' and the resource 'maximum buy/sell quantity for a symbol', making the purpose immediately obvious. It distinguishes itself from sibling tools that perform order placement or data retrieval by emphasizing it is an estimation tool. The return format is also specified.

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 explicitly lists required parameters (symbol, side, order_type) and notes that price is optional, which gives clear guidance on when to use the tool. However, it does not explicitly state when not to use or provide alternatives, though no direct sibling exists for this estimation function.

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