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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so safety and network dependence are covered. The description adds that values are 'as the network publishes them (the fee, or none)', which usefully warns that fees may be absent from the response. It doesn't cover freshness, rate limits, or pagination beyond what the output schema implies.

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 core sentence is front-loaded with the resource list, but it is dense and runs the field enumeration into the scope clause, making it a bit hard to parse. The trailing example question is a helpful anchor rather than waste, but the whole thing is a single overloaded sentence.

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?

An output schema exists, so return shape needn't be explained, and the description covers the fields returned and the 'or none' edge case. For a two-optional-param read tool with full schema coverage and annotations, it is nearly complete; missing only explicit note that all markets are returned when no symbol/pair_id is given.

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 both parameters are documented with examples in the schema itself. The description adds only the 'every market or one' scope framing, implying both params are optional filters. Baseline 3 is appropriate since the schema does the heavy lifting.

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 names a concrete set of resources: maker/taker fees, max leverage, initial and maintenance margin, and liquidation terms, scoped to 'every market or one'. That is a specific verb-less but clear retrieval purpose. It doesn't name a sibling like get_markets to disambiguate (though it references get_markets in the schema), so it falls short of a 5.

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 closing example question ("What does it cost to trade BTC with 10x?") implies when to reach for the tool, and 'for every market or one' signals scope choice. But there's no explicit when-not guidance or named alternative for fee/leverage info elsewhere. Usage is implied rather than stated.

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