binance_check_order_precision

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 that it checks real-time rules, validates precision/limits, and returns a detailed result with suggestions. It does not explicitly state it is non-mutating, but the checking nature and output example make side effects unlikely. No contradiction 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 heavily structured with headings and emojis, and front-loads the core purpose. However, it is overly long due to a massive output example that repeats points and includes non-essential advice. Every sentence does not earn its place, so it's less concise than ideal.

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?

With no output schema, the description compensates with a detailed example return format. It covers what parameters are checked, limitations, and applicable scenarios. However, it lacks failure case examples and doesn't describe error conditions or how to handle invalid symbols, leaving some completeness gaps.

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% and the parameter descriptions are already clear. The tool description adds a comprehensive output example that illustrates how parameters map to results, but it doesn't provide additional semantic detail beyond the schema fields themselves.

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 this tool checks order parameters (price, quantity, limits) against trading pair precision requirements, using specific verbs and resource. It distinguishes itself from siblings like order placement and account info tools by emphasizing pre-order validation.

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 provides explicit applicable scenarios (pre-order validation, manual orders, trading bot risk control) and emphasizes checking before placing orders. It does not explicitly mention alternatives or when not to use, but the context is clear enough.

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