BinanceConvertQueryOrderQuantityPrecisionPerAsset

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

With no annotations, the description carries the sole burden of behavioral disclosure. The verb 'Retrieve' implies a read-only operation, which is a form of transparency, but it does not disclose any further behavioral traits such as rate limits, authentication needs, response structure, or side effects. It is minimally transparent but not rich.

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, concise sentence that is front-loaded with the key information. Every word contributes to clarity, and there is no filler or redundant phrasing.

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 is simple with one optional parameter and no output schema, so the description's mention of 'decimal precision (fraction) information for each supported asset' gives a reasonable expectation of the return concept. However, it lacks any detail about the response format or usage context, which prevents a perfect score.

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% because the only parameter (recvWindow) is fully described in the schema. The description adds no parameter-specific information, but the baseline of 3 applies when the schema already documents parameters sufficiently.

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 ('Retrieve') and a specific resource ('decimal precision (fraction) information for each supported asset in the Convert feature'), clearly distinguishing this tool from sibling Convert tools. It states exactly what the tool does without ambiguity.

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 no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. It simply states the action without context, leaving the agent to infer usage from the name and description alone.

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