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

With no annotations, the description carries the full burden, and it does disclose the returned constraint set plus the real-world failure mode (orders below minNotional are rejected). It omits operational traits such as rate limits, whether results are cached or live, and error behavior for an unsupported exchange.

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?

Three dense sentences with no filler: purpose and returned fields first, the actionable usage cue second, parameter formats last. Every sentence earns its place, including the param block that substitutes for missing enum and schema descriptions.

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?

There is no output schema and no annotations, yet the description lists the fields returned, the accepted values for both parameters, and the practical reason to call it. Nothing an agent needs to invoke or interpret this tool is missing.

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 description coverage is 0% and there are no enums, so the description does all the work: it enumerates every accepted exchange value, including the futures/spot distinction ('binance'=futures, 'binance_spot'), and explains that symbol accepts a base ticker ('BTC') or a pair ('BTCUSDT'/'BTC/USDT'). Without this text an agent could not construct a valid call.

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?

States a specific verb+resource ('Trading rules for a symbol as the EXCHANGE defines them') and enumerates exactly what the rules are: minimum quantity, minimum notional, tick size, and max leverage. This is clearly distinguishable from siblings like get_tickers or get_24h_stats, which return market data rather than venue constraints.

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?

Gives an explicit trigger ('Call this before sizing an order') and the consequence of ignoring it ('a size below minNotional is rejected by the venue'). It does not name an alternative tool or state when this would not be needed, so it stops short of full when/when-not coverage.

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